CC'ing Paolo and xen-devel. Il 14:25, Stefano Stabellini ha scritto: CC'ing Paolo and xen-devel. The original thread is here: On Mon, 2 Dec 2013, Don Slutz wrote: Public bug reported: lt LINK libcacard.la /usr/bin/ld: libcacard/.libs/vcard.o: relocation RX8664PC32 against `vcardbufferresponsedelete' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status make4:.

libcacard.la Error 1 make3:. subdir-libcacard Error 2 Thanks, I'll try to reproduce. Please send the 'make V=1' output for a full build in the meanwhile. Paolo Xen-devel mailing list Xen-devel@lists.xen.org. Il 14:25, Stefano Stabellini ha scritto: CC'ing Paolo and xen-devel. The original thread is here: On Mon, 2 Dec 2013, Don Slutz wrote: Public bug reported: lt LINK libcacard.la /usr/bin/ld: libcacard/.libs/vcard.o: relocation RX8664PC32 against `vcardbufferresponsedelete' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status make4:.

libcacard.la Error 1 make3:. subdir-libcacard Error 2 This is a bug in RHEL5 binutils. Configure with -disable-pie to work around it. Paolo Xen-devel mailing list Xen-devel@lists.xen.org. On 12/03/13 09:06, Paolo Bonzini wrote: Il 14:25, Stefano Stabellini ha scritto: CC'ing Paolo and xen-devel. The original thread is here: On Mon, 2 Dec 2013, Don Slutz wrote: Public bug reported: lt LINK libcacard.la /usr/bin/ld: libcacard/.libs/vcard.o: relocation RX8664PC32 against `vcardbufferresponsedelete' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status make4:.

libcacard.la Error 1 make3:. subdir-libcacard Error 2 Thanks, I'll try to reproduce. Please send the 'make V=1' output for a full build in the meanwhile. Here it is for a full build of:.

Qemu-devel Gcc Detection Fix For Mac Free

7dc65c0 (HEAD, origin/master, origin/HEAD, master) Open 2.0 development tree -Don Slutz Paolo. On 04:18 AM, Paolo Bonzini wrote: $ gcc -shared -o f.so f.c -fPIE -fPIC /usr/bin/ld: /tmp/ccQc9els.o: relocation RX8664PC32 against `f' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status The bug is simply that '-fPIE -fPIC' counts as -fPIE rather than -fPIC: $ gcc -S -o - f.c -fPIE grep call call f # PC32 relocation $ gcc -S -o - f.c -fPIC grep call call f@PLT # PLT32 relocation The easy workaround is to drop -fPIE when we're adding -fPIC. R Xen-devel mailing list Xen-devel@lists.xen.org.

Contents. Install Developer Tools If they didn't come bundled with Mac OS X, get the Xcode Tools (or Developer Tools for older Mac OS X) from or from your install disk.

This will install Apple versions of:. (GNU Compilers). (GNU Debugger). (GNU Make) Apple regularly pulls all older links in order to promote newer Mac OS X, but all the old developer tools can be downloaded from ADC at You need a (free) developer registration with Apple first, in order to log in there. For Mac OS X 10.4, you want (at least) Xcode 2.2, since earlier versions were buggy.

Check Autotools versions Depending on your OS version, you might need to download and compile new versions of these:. (GNU Autoconf). (GNU Automake). (GNU Libtool) Check what you have, with -version (note that GNU libtool is called 'glibtool' on Mac OS X) Currently Code::Blocks requires versions:. autoconf 2.50+. automake 1.7+ (1.9+ needed in order to build the dist tarball).

libtool 1.4+ (1.5.8+ highly recommended to get some bug fixes) Automake example For Mac OS X 10.4, you will only need an upgraded (local) installation of automake 1.9.x. You can download ' and configure and install it with something like:./configure -prefix=/usr/local -program-suffix=-1.9 make sudo make install sudo cp -pi /usr/share/aclocal/libtool.m4 /usr/local/share/aclocal-1.9/ Since it's now known as 'automake-1.9', it won't interfere with the regular 'automake' If you would rather have the new version to be called when calling 'automake', let it install into /usr/local and put /usr/local/bin before /usr/bin in your PATH. Libtool example Download source. The following instructions will overwrite your current version of libtool with the one you just downloaded. Cd /libtool-././configure -prefix=/usr -program-prefix=g make sudo make install Note that this will replace the system version of glibtool, which might have some compatibility issues with building other software.

Qemu-devel Gcc Detection Fix For Mac Pro

Download asp net core. FYI: Universal Binaries If you are building for Mac OS X 10.4 or later, you might want to build ' These are binaries that contain code for both PowerPC ('ppc' arch) and Intel ('i386' arch) The basic flags that needs to be added are: CFLAGS += '-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc' CXXFLAGS += '-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc' (You only need the sysroot parameter on PowerPC Macintosh, not on a Intel Macintosh) The '-arch i386 -arch ppc' is what tells the compiler to build a 'universal' (or 'fat') binary. Usually it's easiest to build one version for 'powerpc-apple-darwin8', and one version for 'i686-apple-darwin8', and then merge them with './configure -host=powerpc-apple-darwin8 -target=powerpc-apple-darwin8./configure -host=i686-apple-darwin8 -target=i686-apple-darwin8 Some caveats:. pre-compiled headers might fail with a 'no main' error. If they do, add a -c to only compile them. when cross-compiling, tools like autorevision might fail to build. Copy these from a native build.

the Tiger compilers might crash from time to time, but that is only to be expected (it seems). See: Building Universal Binaries from 'configure'-based Open Source Projects FYI: Compilers When building for older versions of the SDK, you want to make sure to use the same compiler.

CC = gcc-4.0 CXX = g-4.0 Mac OS X 10.6 has GCC 4.2 as the default compiler, which won't work for the Mac OS X 10.4 SDK. FYI: ANSI or UNICODE For the moment we are using 'ANSI' (-disable-unicode, default) for Mac OS X 10.3 and earlier, and 'UNICODE' (-enable-unicode, optional) for Mac OS X 10.4 and later. See FYI: 32-bit or 64-bit Code::Blocks currently uses wxMac (wxOSX/Carbon), which is 32-bit only.

So it's not possible to build for 'x8664'. When Code::Blocks (and requirements) has been updated to use wxOSX/Cocoa, then a 64-bit version might be built too.

Build wxWidgets Download the source code Download the tarball for the wxMac release: Apply necessary patches Don't forget to apply any released patches!