search for: xgcc

Hi Guys I'm trying to port and build the GCC Front End to the Interix environment. I've succeded until the xgcc program executes: /usr/local/src/cfrontend/build/gcc/xgcc -B/usr/local/src/cfrontend/build/gcc/ -B/usr/local/src/cfrontend/install//i586-pc-interix3/bin/ -B/usr/local/src/cfrontend/install//i586-pc-interix3/lib/ -isystem /usr/local/src/cfrontend/install//i586-pc-interix3/include -isystem /usr...

Reid Spencer wrote: > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > When you run it from the command line it will find yoursystem libgcc.so (which works) Not really. For systems that have gcc 4.2 natively installed, like the current Debian testing, the compiler gets GCC_4.2.0 version errors. It isn't easy to...

...cache ./config.cache checking for --enable-version-specific-runtime-libs... no checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for i686-pc-linux-gnu-gcc... /home/pmallapp/tmp/llvm-gcc-build/gcc/xgcc -B/home/pmallapp/tmp/llvm-gcc-build/gcc/ -B/tmp/llvm-gcc/i686-pc-linux-gnu/bin/ -B/tmp/llvm-gcc/i686-pc-linux-gnu/lib/ -isystem /tmp/llvm-gcc/i686-pc-linux-gnu/include -isystem /tmp/llvm-gcc/i686-pc-linux-gnu/sys-include checking for C compiler default output file name... a.out checking whether the...

...ck-in? -bw Begin forwarded message: > From: admin at spang.apple.com (admin) > Date: March 4, 2009 3:56:10 AM PST > To: wendling at apple.com > Subject: PPC Nightly Build Result > > /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj- > powerpc-powerpc/./prev-gcc/xgcc -B/Volumes/SandBox/NightlyTest/ > llvmgcc42.roots/llvmgcc42~obj/obj-powerpc-powerpc/./prev-gcc/ -B/ > Developer/usr/llvm-gcc-4.2/powerpc-apple-darwin9/bin/ -c -g -O2 - > mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict- > prototypes -Wmissing-prototypes -pedantic -Wno-...

...age: > > > From: ad... at spang.apple.com (admin) > > Date: March 4, 2009 3:56:10 AM PST > > To: wendl... at apple.com > > Subject: PPC Nightly Build Result > > > /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj- > > powerpc-powerpc/./prev-gcc/xgcc -B/Volumes/SandBox/NightlyTest/ > > llvmgcc42.roots/llvmgcc42~obj/obj-powerpc-powerpc/./prev-gcc/ -B/ > > Developer/usr/llvm-gcc-4.2/powerpc-apple-darwin9/bin/ -c   -g -O2 - > > mdynamic-no-pic -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict- > > prototypes -Wmissing-prototypes...

...sr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext x86_64-unknown-linux-gnu checking for msgmerge... checking host system type... /usr/bin/msgmerge x86_64-unknown-linux-gnu checking for x86_64-unknown-linux-gnu-gcc... /home/alan/pkg/llvm/obj/./prev-gcc/xgcc -B/home/alan/pkg/llvm/obj/./prev-gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ checking for C compiler default output file name... checking for x86_64-unknown-linux-gnu-ar... ar checking for x86_64-unknown-linux-gnu-ranlib... ranlib checking for x86_64-unknown-linux-gnu-gcc... /home/alan/pkg/llv...

...From: ad... at spang.apple.com (admin) >>> Date: March 4, 2009 3:56:10 AM PST >>> To: wendl... at apple.com >>> Subject: PPC Nightly Build Result >> >>> /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj- >>> powerpc-powerpc/./prev-gcc/xgcc -B/Volumes/SandBox/NightlyTest/ >>> llvmgcc42.roots/llvmgcc42~obj/obj-powerpc-powerpc/./prev-gcc/ -B/ >>> Developer/usr/llvm-gcc-4.2/powerpc-apple-darwin9/bin/ -c -g -O2 - >>> mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict- >>> prototypes -Wmissin...

Hi Jack, > Actually, shouldn't this be just an error in the Makefile.in or > Makefile.am? Why should a link line like... ... > ..even require c++ instead of xgcc? because xgcc may not support c++. I'm not saying that it can't be done, just that it has not been done. Like anything, someone has to sit down and do it, and nobody has done so yet. Ciao, Duncan.

Hi Scooter, On Mon, 2006-11-06 at 12:07 -0800, Scott Michel wrote: > Reid Spencer wrote: > > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > > When you run it from the command line it will find yoursystem > libgcc.so (which works) > > Not really. For systems that have gcc 4.2 natively installed, like the > current Debian testing, the compiler gets GCC_4.2.0 version err...

...llvm/obj.llvm \ --program-prefix=llvm- \ --enable-languages=c,c++ \ --disable-bootstrap \ --disable-shared make ---------------------------------- This takes some time, and then I get this: ---------------------------------- if /bin/sh ./libtool --mode=compile /s/llvm/obj.gcc42/./gcc/xgcc -B/s/llvm/obj.gcc42/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/include -isystem /usr/local/i686-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/s/llvm/svn.gcc42/libgomp -I. -I/s/llvm/svn.gcc42/libgomp/config/linux/x86 -I/s/l...

This is an libpath problem. When xgcc runs it wants to dynamically link the libgcc.so. When you run it from the command line it will find your system libgcc.so (which works) and so you don't see the segfault. When you run xgcc from the Makefile, it will have set LD_LIBRARY_PATH to get your <cfebuilddir>/gcc directory which w...

...tem.a attribs.o stub-objc.o stub-c.o -L/sw/lib -lmpfr -lgmp ../libcpp/libcpp.a ./../intl/libintl.a /usr/lib/libiconv.dylib ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -L/sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib -lpthread -lm ..even require c++ instead of xgcc? Jack On Mon, Aug 11, 2008 at 04:18:00PM +0200, Duncan Sands wrote: > > the FSF gcc requires you to build the C compiler (I think - will check). > Thus a newly built C compiler is always available to build later stages. > We can't reasonably require ev...

...response I've removed the #undef DBX_DEBUGGING_INFO in > gcc/config/ia64/sysv4.h. I don't need stabs debugging so if it is > broken > in my final build, I won't care. After doing so, my llvm-gcc build > runs > for a much longer time before finally dying while running xgcc. Here > is > the final output: > > /liberty/llvm.ia64/obj/./gcc/xgcc -B/liberty/llvm.ia64/obj/./gcc/ > -B/liberty/llvm.ia64/obj/../install/ia64-unknown-linux-gnu/bin/ > -B/liberty/llvm.ia64/obj/../install/ia64-unknown-linux-gnu/lib/ - > isystem > /liberty/llvm.ia64/obj/.....

I've been unable to bootstrap llvm-gcc-4.0 or -4.2 for x86_64 for some weeks now. The current problem is this: [x86_64-mod-dbg]: ./xgcc -B./ -B/install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/ -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/include -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/sys-include -L/tmp/ptmp/dag/build.l...

...llvm-gcc4. Here's the text of the patch, for those that are building llvm-gcc4: On more recent systems (e.g. Fedora Core 5), where the version of libgcc_s.so used by libstdc++.so is more recent than the version used by llvm-gcc, you will get an error when building llvm-gcc that looks like: xgcc: .../gcc/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) This happens because the xgcc program dynamically links in libstdc ++.so.6 which requires libgcc_s.so. When xgcc was built, it found the libgcc_so that your compiler uses. But, when xgcc runs, it fin...

On Thu, 28 Sep 2006, Nick Lewycky wrote: > Thanks for that workaround. What I've been doing is copying > /lib/libgcc_s.so.1 over LLVM's copy and rebuilding xgcc. > > A long-term fix for this would be nice. I'm not hitting this, so I'm relying on you guys to figure out what the right solution is. > Why does llvm-gcc build its own libgcc_s.so? Would we have the same > problem if we tried to build FSF GCC 4.01, or is this problem LLVM-s...

Hello, Aaron. > This is still at the stage of using xgcc.exe AFAICT before any LLVM bytecode > generation. Yep. But xgcc generates code via LLVM! So, you can just copy command line from your terminal, add -emit-llvm, run it and you'll see, that resulting .o will be LLVM bytecode (or won't if FE will crash). > __eprintf is a very simple fu...

...problems. > I'm not sure how robust the ia64 implementation is. > > Configuring with > BOOTSTRAP= > should stop it from trying to bootstrap. However, it's still likely > to try to build the file that's causing trouble. > Is there any reason why I can't use xgcc to generate LLVM bitcodes? What are the limitations of xgcc relative to gcc? Tom

Hi Owen, I'm seeing this failure on one of my machines -- PPC G5: $ # APPLE LOCAL use -mlongcall for large text support /Volumes/SandBox/Clean/bug/llvm-gcc.obj/./gcc/xgcc -B/Volumes/SandBox/Clean/bug/llvm-gcc.obj/./gcc/ -B/Volumes/SandBox/Clean/bug/llvm-gcc.install/powerpc-apple-darwin9.1.0/bin/ -B/Volumes/SandBox/Clean/bug/llvm-gcc.install/powerpc-apple-darwin9.1.0/lib/ -isystem /Volumes/SandBox/Clean/bug/llvm-gcc.install/powerpc-apple-darwin9.1.0/include -isystem...

David Greene wrote: > I'm getting the following when building llvm-gcc with an optimized set of > LLVM libraries: > > /ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/xgcc > -B/ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/ > -B/cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/ > -B/cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.officia...