Displaying 20 results from an estimated 89762 matches for "developements".
Did you mean:
developement
2012 Feb 27
2
Is there an easier way of doing this?
I'm trying to compile the latest wine release from source after a fresh linux mint install, and this is what I get when I do './configure'
Code:
configure: libxcursor development files not found, the Xcursor extension won't be supported.
configure: libxi development files not found, the Xinput extension won't be supported.
configure: XShape development files not found, XShape
2011 Jun 09
3
Compiling wine: no sound system, etc.
Hello all...
I'm trying to compile wine 1.3.21 on my Linux Mint Debian Edition machine, because I'm tired of the antique version available from the repositories. Unfortunately, ./configure always ends with a bunch of WARNINGs and I'm not sure what to do about them. Here's the list it gives me:
Code:
configure: libxcursor development files not found, the Xcursor extension won't
2011 Jan 18
2
"Problem installing wine"
config.status: linking AUTHORS to dlls/shell32/AUTHORS
config.status: linking tools/winewrapper to wine
config.status: executing include/stamp-h commands
config.status: executing dlls/gdi32/enhmfdrv commands
config.status: executing dlls/gdi32/mfdrv commands
config.status: executing dlls/kernel32/nls commands
config.status: executing dlls/user32/resources commands
config.status: executing
2020 May 07
2
Ld64.lld cannot find Foundation framework
Dear LLVM community I need some help please.
I want to use LLVM's clang and lld within a MacOSX sandboxed app. This is because sandboxing does not allow calls to /usr/bin/clang.
The clang binary works fine to compile a file, but ld64.lld comes up with the error "cannot find framework".
However similar arguments using /usr/bin/ld instead of ld64.lld works fine.
Here are the
2012 Jul 20
9
[LLVMdev] RFC: Staging area proposal for new backends
Hi,
I would like to follow up on the recent discussion on the mailing list
about requirements for new backends[1] by submitting the following
proposal for a staging area for new LLVM backends. This proposal
incorporates ideas from Owen, Chandler, and others who chimed in on
the original thread, and I hope the LLVM developers will be able to
come to a consensus on this proposal or a modified
2007 Jun 11
12
Mocking system/`
This drives me insane on a regular basis. How does one mock
system(''blah'') or `blah` ?
Adding expectations on Kernel doesn''t do it. Adding expectations on
Object just makes me sad:
Object.any_instance.expects(:system).with(''ls'')
# => #<Mock:0x12b584e>.system(''ls'') - expected calls: 0, actual calls: 1
And this really
2008 May 15
8
Call for help with Wine 1.0 testing
Hi Folks,
One key goal for Wine 1.0 is that all of its conformance
tests run successfully on nearly all systems. We would really like
your help in figuring out how close we are to that goal.
To that end, if you are comfortable with checking Wine out via git,
could you please visit this page:
http://wiki.winehq.org/MakeTestFailures
and follow the instructions there? (It's really simple;
2006 Aug 03
14
What OS do you use for development?
Just out of curiousity, what OS do most of you use for development? Do
you prefer to use WinXP to do your development, and then deploy to a
linux server, or do you actually use some distribution of linux (Ubuntu,
Debian, Gentoo, etc) for development?
Thanks!
--
Posted via http://www.ruby-forum.com/.
2012 Jan 30
1
Wine 1.4: Not Installing
Error:
Code:
checking for freetype-config... no
checking for freetype2-config... no
checking for -lfreetype... not found
configure: error: FreeType development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
I tried using the option:
Code:
./tools/wineinstall --without-freetype
Same error.
2008 Oct 21
4
[LLVMdev] Replacing llvm-gcc in Xcode 3.1.1 with svn version
Hello all,
I have replaced the llvm-gcc shipped with the Xcode by the latest
version and I was wondering if I have missed something... (everything
*seems* to work).
Here's what I did:
0. Checkout LLVM (and clang) + llvm-gcc
1. Build LLVM (with clang) and install into /Developer/usr/local :
# mkdir llvmobj
# cd llvmobj
# CC=gcc-4.2 CXX=g++-4.2 ../llvm/configure
2012 Sep 06
0
[LLVMdev] RFC: Staging area proposal for new backends
Hi,
Now that --enable-experimental-targets build flags have been added to
the build systems. What needs to be done in order to get the R600
backend added as an experimental target? I've posted an updated
version of the backend to llvm-commits[1], that addresses many of the
criticisms of the backend, but I haven't received any feedback, and I
feel like the submission process has stalled.
2012 Jul 27
0
[LLVMdev] RFC: Staging area proposal for new backends
Hi,
I would like to try to keep the staging area discussion going. There
seems to be a general consensus that a staging area for backends and also
new features would be acceptable for the LLVM project. What actions
are required to make the staging area a reality? Is more discussion
needed? Is anyone willing to volunteer to be the "Code Owner" for the
staging area, to help move the
2012 Sep 08
1
[LLVMdev] RFC: Staging area proposal for new backends
Dear Tom,
Looks like setting LCOMMDirectiveType in AMDGPUMCAsmInfo.cpp is not
needed anymore? I commented it out, and then LLVM got compiled fine.
- D.
2012/9/6 Tom Stellard <tstellar at gmail.com>:
> Hi,
>
> Now that --enable-experimental-targets build flags have been added to
> the build systems. What needs to be done in order to get the R600
> backend added as an
2006 Sep 16
1
[LLVMdev] cpp program linking error
Hi,
i have compile and built the llvm-gcc4 and llvm 1.8a in my machine, but
there is some problem about llvm-gcc4. It can not compile a
cpp code like this:
#include <iostream>
using std::cout;
using std::endl;
int main()
{
cout << "Hello" << endl;
}
$llvm-g++ hello.cc -o hello
/developer/zsth/llvm-gcc/install/bin/../lib/gcc/i686-pc-linux-gnu/4.0.1/../../..
2016 Oct 04
3
Software tools development opportunity at Qualcomm in Austin
Hi folks,
I'm looking for a developer to join my team in Austin to help develop linker
back ends for ARM and AArch64. Given that this is the LLVM dev list, I want
to be clear that the work involves close collaboration with our internal
LLVM teams so LLVM experience is a definite plus, but it does not involve
direct development on LLVM.
I'm ideally looking for someone with direct
2006 Mar 29
38
Poll: Which distro do you use for Rails/Ruby development?
Good afternoon,
I''ve two quick questions for the Ruby/Rails community.
1) Do you use Linux for Ruby or Rails development?
2) If you use Linux, which distro do you normally use to develop?
Thank you for your input. :-)
--
Posted via http://www.ruby-forum.com/.
2015 Feb 12
4
[LLVMdev] Building clang on Raspberry Pi2
The raspberry Pi2 is an armv7a chip (Cortex-A7), the first stage builds
fine with the native g++ (if not a little slowly at 10+ hours), but it
crashes at some point with this command line:
Program arguments:
/home/ben/development/llvm/3.6.0/rc2/Phase2/Release/llvmCore-3.6.0-rc2.install/bin/clang
-cc1 -triple armv7-unknown-linux-gnueabihf -emit-obj -disable-free
-disable-llvm-verifier
2006 Oct 16
3
Strange ActiveRecord error popping up
Hello guys, I''m developing a new app in Rails, and every now and then
I get an ActiveRecord error, I cannot reproduce exactly what triggers
it, hope you can help me, or give me tips on debugging this kind of
stuff. This time I got the error reporting page, but normally I would
just see the 500.html page, with no info about what went wrong.
This is the error (it''s the complete
2009 Oct 25
2
[LLVMdev] configuring LLVM 2.6 for OSX 10.4sdk on OSX 10.5 system
Hi all,
(Sorry if the answer to this is obvious - and thanks in advance~)
Short version:
linker error of _backtrace from LLVMSystem.a building a dynamic
library embedding LLVM/clang, both against the OSX 10.4 sdk.
Long version:
I've just tried rebuilding my project using the 2.6 release, using the
following commands to try and force LLVM to build against the OSX 10.4
sdk (I am
2012 Jul 27
2
[LLVMdev] RFC: Staging area proposal for new backends
On 07/27/2012 01:01 PM, Tom Stellard wrote:
> Hi,
>
> I would like to try to keep the staging area discussion going. There
> seems to be a general consensus that a staging area for backends and also
> new features would be acceptable for the LLVM project. What actions
> are required to make the staging area a reality? Is more discussion
> needed? Is anyone willing to