Successful build of gcc 12.1 on Linux

* Output from running srcdir/config.guess. Do not send that file itself, just the one-line output from running it. * x86_64-pc-linux-gnu * The output of ‘gcc -v’ for your newly installed gcc. This tells us which version of GCC you built and the options you passed to configure. * U

Successful build and install of gcc 10.0.1.0

Hello, Following the instructions given in the install folder for gcc 10.1.0, I have successfully bootstrapped and installed gcc 10.1.0. Below is the information requested in the final install section: The output of config.guess is: x86_64-pc-linux-gnu The output of gcc -v is: Using built-in s

Build Status - Successful Build & Install

srcdir/config.guess: x86_64-pc-linux-gnu gcc -v output: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../srcdir/configure --disable-multilib Thread model: posix gcc version 9.2.0 (G

Successful build of gcc 9.2.0 on x86_64-w64-mingw32

Testresults can be seen here: https://gcc.gnu.org/ml/gcc-testresults/2019-08/msg01595.html Complete logs of the testsuite run are available here: https://cloud.emrich-ebersheim.de/index.php/s/g9D245XdCW6GD5W signature.asc Description: OpenPGP digital signature

Successful build and some autotuning of GCC 7.1.0 on Raspberry Pi 3

Dear GCC colleagues, I managed to build GCC 7.1.0 on Raspberry Pi 3 (Raspbian GNU/Linux 8 (jessie), GCC 4.9.2). It required combination of specific configuration flags: --with-cpu=cortex-a53 --with-fpu=neon-fp-armv8 --with-float=hard --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --

successful build and install

Here is info according to installation document on your homepages: ___ srcdir/config.guess: x86_64-unknown-linux-gnu gcc -v: Using built-in specs. COLLECT_GCC=./gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wra

GCC 4.6.3 successful build on i386-apple-darwin10.8.0

i386-apple-darwin10.8.0 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/Cellar/gcc/4.6.3/bin/../libexec/gcc/i386-apple-darwin10.8.0/4.6.3/lto-wrapper Target: i386-apple-darwin10.8.0 Configured with: ../gcc-4.6.3/configure --prefix=/usr/local/Cellar/gcc46 --enable-languages=all

Re: GCC 4.6 Successful Build and Install

===-==- > ii libc6 2.11.1-0ubuntu Embedded GNU C Library: Shared libraries > > Misc: > > I had to install package: libc6-dev-i386 to get a successful build. > > Goal: working gccgo > > Results: > > - Simple go programs compile > - Need to use LD_LIBRARY_PATH to get executables to run > > >

GCC 4.6 Successful Build and Install

2.11.1-0ubuntu Embedded GNU C Library: Shared libraries Misc: I had to install package: libc6-dev-i386 to get a successful build. Goal: working gccgo Results: - Simple go programs compile - Need to use LD_LIBRARY_PATH to get executables to run

Successful build

I first installed gcc 4.5.0 on my Powerpc dual 970 machine with no configuration options. That was successful, but the long long feature was not enabled. Then I re-installed gcc 4.5.0 with this gcc ­v output: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/powerpc-

successful build

Hi list, the 4.3.0 version compiled and installed without promblems, using msys under WindowsXP SP2. Thanks to the GCC team! $ gcc -v Using built-in specs. Target: mingw32 Configured with: ../gcc-4.3.0/configure --with-gcc --build=mingw32 --prefix=/mingw --with-mpfd=/usrlocal --with-gmp=/usrl

Successful Build

i386-unknown-netbsdelf4.99.35 Using built-in specs. Target: i686-pc-netbsdelf4.99.35 Configured with: ../gcc-4.2.2/configure --prefix=/usr/local/opt/gcc-4.2.2 --target=i686-pc-netbsdelf4.99.35 --build=i686-pc-netbsdelf4.99.35 --host=i686-pc-netbsdelf4.99.35 --enable-threads --enable-tls --with-

A compensation to 'Successful Build Report for GCC 4.0.0 C and C++'

Hello: This is a compensation to Simon G. Best's build report (http://gcc.gnu.org/ml/gcc/2005-04/msg01402.html). As Simon G. Best mentioned, after final-install, gcc's shared libs should be configed as below: 1. add the line '/usr/local/lib' to the end of '/etc/ld.so.conf'; 2. run 'ldconfig'

Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

Aaron Gray wrote: One issue that might affect many some is that COM doesn't work. has a patch that is pending review I guess, but probably won't go into 4.2. Does this effect XPCOM meaning Mozilla and friends will not compile ? It is trig

Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

Aaron Gray wrote: One issue that might affect many some is that COM doesn't work. has a patch that is pending review I guess, but probably won't go into 4.2. Does this effect XPCOM meaning Mozilla and friends will not compile ? It is trig

Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

Aaron Gray wrote: One issue that might affect many some is that COM doesn't work. has a patch that is pending review I guess, but probably won't go into 4.2. Does this effect XPCOM meaning Mozilla and friends will not compile ? It is trig

Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

Hi Aaron, One issue that might affect many some is that COM doesn't work. has a patch that is pending review I guess, but probably won't go into 4.2. Its not a very big patch, shame it cannot be reviewed in time. Does this effect XPCOM mean

Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

- Original Message - From: "Dave Korn" <[EMAIL PROTECTED]> To: "'Dave Korn'" <[EMAIL PROTECTED]>; "'Aaron Gray'" <[EMAIL PROTECTED]> Cc: "'GCC'" Sent: Sunday, May 06, 2007 4:10 PM Subject: RE: Succes

RE: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

On 06 May 2007 15:54, Dave Korn wrote: [ Cygwin list snipped from CC line: not relevant there. ] > > If you can produce once that shows excess warnings being emitted, yes, > that would be worth filing a PR. Hmm, a quick test I couldn't get excess > ones, but the line numbers all look wrong..

RE: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

On 06 May 2007 14:37, Aaron Gray wrote: > On the LLVM build I am getting multiple :- > > warning: visibility attribute not supported in this configuration; > ignored > > with the same line number, eight or so in some cases but usually two. > > Have not looked into this properly yet, I misse

Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

On 06 May 2007 07:15, Aaron Gray wrote: I have successfully built GCC-4.2.0-20070501 on latest Cygwin snapshot 20070427. GCC 4.2.0 RC3 is available from: ftp://gcc.gnu.org/pub/gcc/prerelease-4.2.0-20070501 I have not done run the testsuite ( make check) I'm doing that. Should be f

RE: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

On 06 May 2007 07:15, Aaron Gray wrote: > I have successfully built GCC-4.2.0-20070501 on latest Cygwin snapshot > 20070427. > > GCC 4.2.0 RC3 is available from: > > ftp://gcc.gnu.org/pub/gcc/prerelease-4.2.0-20070501 > > I have not done run the testsuite ( make check) I'm doing tha

Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427

I have successfully built GCC-4.2.0-20070501 on latest Cygwin snapshot 20070427. GCC 4.2.0 RC3 is available from: ftp://gcc.gnu.org/pub/gcc/prerelease-4.2.0-20070501 I have not done run the testsuite ( make check) but have built LLVM and LLVM-GCC4. So indications are very good. Aaron

Successful build of 4.2.0 RC2 for target=avr host=mingw

...well sort of. If I use the releases straight, I get this: In file included from ../../gcc-4.2.0-20070430/gcc/libgcc2.c:35: ./tm.h:5:29: error: config/avr/avr.h: No such file or directory ./tm.h:6:28: error: config/dbxelf.h: No such file or directory ./tm.h:7:31: error: config/tm-dwarf2.h: No s

Re: Build report: Successful build of gcc 4.1.2 on Cygwin (Win XP Pro SP2)

Brian Dessent wrote: "Aaron W. LaFramboise" wrote: I don't really see any compelling reason that win32 threads shouldn't work on Cygwin. As far as I know, nothing about this choice is ultimately exposed to the user. In fact, Win32 threads are quite likely to yield superior performance anywher

Build report: Successful build of gcc 4.1.2 on Cygwin (pthreads)

I built gcc 4.1.2 again on Cygwin but this time with pthreads. No problems at all during compilation. Output of config.guess: i686-pc-cygwin Output of gcc -v: Using built-in specs. Target: i686-pc-cygwin Configured with: /home/jesper/gcc-4.1.2/configure --enable-threads=posix --with-cpu=i686 -

Re: Build report: Successful build of gcc 4.1.2 on Cygwin (Win XP Pro SP2)

"Aaron W. LaFramboise" wrote: > I don't really see any compelling reason that win32 threads shouldn't > work on Cygwin. As far as I know, nothing about this choice is > ultimately exposed to the user. In fact, Win32 threads are quite likely > to yield superior performance anywhere where it matte

Re: Build report: Successful build of gcc 4.1.2 on Cygwin (Win XP Pro SP2)

Brian Dessent wrote: Jesper de Jong wrote: /home/jesper/gcc-4.1.2/configure --enable-threads=win32 Where do people keep getting this idea that Cygwin uses win32 threads? It doesn't, and you've most likely built a compiler that is subtly broken in some way. Cygwin uses pthreads, this sh

Re: Build report: Successful build of gcc 4.1.2 on Cygwin (Win XP Pro SP2)

Hello Brian, Maybe because the configuration instructions: http://gcc.gnu.org/install/configure.html suggest that there is a choice and if you don't know better you will think "I'm using Windows so I can use win32 threads". Jesper 2007/4/5, Brian Dessent <[EMAIL PROTECTED]>: Jesper de Jong wro

RE: Build report: Successful build of gcc 4.1.2 on Cygwin (Win XP Pro SP2)

On 05 April 2007 13:52, Brian Dessent wrote: > Jesper de Jong wrote: > >> /home/jesper/gcc-4.1.2/configure --enable-threads=win32 > > Where do people keep getting this idea that Cygwin uses win32 threads? > It doesn't, and you've most likely built a compiler that is subtly > broken in some w

Re: Build report: Successful build of gcc 4.1.2 on Cygwin (Win XP Pro SP2)

Jesper de Jong wrote: > /home/jesper/gcc-4.1.2/configure --enable-threads=win32 Where do people keep getting this idea that Cygwin uses win32 threads? It doesn't, and you've most likely built a compiler that is subtly broken in some way. Cygwin uses pthreads, this should be --enable-threads

Build report: Successful build of gcc 4.1.2 on Cygwin (Win XP Pro SP2)

I successfully build gcc-4.1.2 on Cygwin running on Windows XP Professional with SP2. Output from running /home/jesper/gcc-4.1.2/config.guess: i686-pc-cygwin Output of 'gcc -v': Using built-in specs. Target: i686-pc-cygwin Configured with: /home/jesper/gcc-4.1.2/configure --enable-th

Successful build/install of gcc-4.1.2 on Solaris10

Successful build/install of gcc-4.1.2 on Solaris10 The previous version of GCC used for the build was 3.4.6 I just built the compiler until I worked around the toolchain problems: downrev gawk and missing gmp (watch 32 vs 64 bit) and mpfr. Then a reconfig for everything built and installed in

gcc 4.1.2 - successful build and install - i386-pc-mingw32 (msys running on a WinXP box)

Follows the build info: config.guess: i386-pc-mingw32 $ gcc -v Using built-in specs. Target: mingw32 Configured with: ../../source/gcc-4.1.2/configure --prefix=/mingw --host=mingw32 --target=mingw32 --program-prefix="" --with-gcc --with-gnu-ld --with-gnu-as --enable-threads --disable-nls --enab

gcc 4.2.0-20060902 - i386-pc-mingw32 - successful build and install

Follows the build info: config.guess: i386-pc-mingw32 $ gcc -v Using built-in specs. Target: mingw32 Configured with: ../../source/gcc-4.2-20060902/configure --prefix=/mingw --host=mingw32 --target=mingw32 --program-prefix="" --with-as=/mingw/bin/as.exe --with-ld=/mingw/bin/ld.exe --with-gcc --

gcc 4.2.0-20060826 - successful build and install - i386-pc-mingw32 (msys at a WinXP box)

Follows the build info: config.guess: i386-pc-mingw32 $ gcc -v Using built-in specs. Target: mingw32 Configured with: ../../source/gcc-4.2-20060826/configure --prefix=/mingw --host=mingw32 --target=mingw32 --program-prefix="" --with-as=/mingw/bin/as.exe --with-ld=/mingw/bin/ld.exe --with-gcc --

gcc 4.1.1 - successful build and install - i386-pc-mingw32 (msys running on a WinXP box)

Follows the build info: config.guess: i386-pc-mingw32 $ gcc -v Using built-in specs. Target: mingw32 Configured with: ../../source/gcc-4.1.1/configure --prefix=/mingw --host=mingw32 --target=mingw32 --program-prefix="" --with-gcc --with-gnu-ld --with-gnu-as --enable-threads --disable-nls --enab

Re: Successful Build: gcc-4.1-20051230 i686-pc-mingw32

ake[1]: *** [stage2_build] Error 2 make[1]: Leaving directory `/home/schuttek/gcc-4.1.1-build/gcc' make: *** [bootstrap] Error 2 Anyone an idea how to solve this? I -- View this message in context: http://www.nabble.com/Successful-Build%3A-gcc-4.1-20051230-i686-pc-mingw32-tf834182.html#a6058353 Sent from the gcc - Dev forum at Nabble.com.

gcc 4.1.1 Successful build - Cedric Arbogast

Hello, GCC 4.1.1 have successfully compiled on this system : ./config.guess: i686-pc-linux-gnu GCC_EXEC_PREFIX=/usr/local/gcc411; export GCC_EXEC_PREFIX; gcc -v : Using built-in specs. Target: i686-pc-linux-gnu Configured with: /usr/src/gcc-4.1.1/configure --prefix=/usr/local/gcc411 --enable-

Re: Successful Build: gcc-4.1-20051230 i686-pc-mingw32

Thank you. Now it compiled and i built my first testfile. I only extracted the mingw-runtime and w32api into the --prefix directory. bye -- View this message in context: http://www.nabble.com/Successful-Build%3A-gcc-4.1-20051230-i686-pc-mingw32-t834182.html#a3317635 Sent from the gcc - Dev

Re: Successful Build: gcc-4.1-20051230 i686-pc-mingw32

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Incognito wrote: > > I started again (deleted the generated files) and configured with "sh > ../gcc-4.1.0/configure --prefix=/home/gcc41 --enable-threads=win32 > --with-ld=/mingw/bin/ld --with-win32-nlsapi=unicode" and fired "make > bootstrap". I thin

Re: Successful Build: gcc-4.1-20051230 i686-pc-mingw32

> I started again (deleted the generated files) and configured with "sh > ../gcc-4.1.0/configure --prefix=/home/gcc41 --enable-threads=win32 > --with-ld=/mingw/bin/ld --with-win32-nlsapi=unicode" and fired "make > bootstrap". I think this time make made more than the last time, but ejected > an err

Re: Successful Build: gcc-4.1-20051230 i686-pc-mingw32

rectory `/home/gcc41-obj/gcc' make: *** [bootstrap] Error 2 I hope I'm not wasting your time with such trivial things... bye -- View this message in context: http://www.nabble.com/Successful-Build%3A-gcc-4.1-20051230-i686-pc-mingw32-t834182.html#a3300867 Sent from the gcc - Dev forum at Nabble.com.

Re: Successful Build: gcc-4.1-20051230 i686-pc-mingw32

[sorry for breaking the thread, stupid gmail interface doesn't allow adding custom headers] > i tried to compile gcc 4.1.0 (the final release) on windows, too. I'm using > msys and configured the buildprocess with "--enable-threads=win32 > --with-win32-nlsapi=unicode". On the msys console i type "

Re: Successful Build: gcc-4.1-20051230 i686-pc-mingw32

? bye -- View this message in context: http://www.nabble.com/Successful-Build%3A-gcc-4.1-20051230-i686-pc-mingw32-t834182.html#a3296497 Sent from the gcc - Dev forum at Nabble.com.

successful build of mingw hosted arm-elf GCC 4.1.0 RC1

output of config.guess $ gcc-4.1.0-20060219/config.guess i686-pc-mingw32 $ arm-elf-gcc -v Using built-in specs. Target: arm-elf Configured with: ../../gcc-4.1.0-20060219/configure --enable-languages=c,c++ --with-cpu=arm7tdmi --enable-interwork --enable-multilib --with-gcc --with-gnu-ld --with-

Successful Build

*** config.guess: i686-pc-linux-gnu *** GCC version: Using built-in specs. Target: i686-pc-linux-gnu Configured with: /home/dinosaur/tmp/gcc/src/configure Thread model: posix gcc version 4.0.2 *** Distribution name and version: Mandrakelinux release 10.2 (Limited Edition 2005) for i586 Kernel 2.

Successful Build

*** config.guess: i686-pc-linux-gnu *** GCC version: Using built-in specs. Target: i686-pc-linux-gnu Configured with: /home/dinosaur/tmp/gcc/src/configure Thread model: posix gcc version 4.0.2 *** Distribution name and version: Mandrakelinux release 10.2 (Limited Edition 2005) for i586 Kernel 2.

Successful build of gcc 3.4.4 [alphaev56-dec-osf5.1]

Hi, I've successfully built gcc 3.4.4 on Tru64 5.1B alphaev56-dec-osf5.1 which is not currently on your build page. http://gcc.gnu.org/gcc-3.4/buildstat.html Sorry - no test results, but I have since used it to build cvsnt 2.5.03.2214 and it all seems to work... * Output from running srcdir/co

Successful build and install of gcc-3.4.5

> ./config.guess x86_64-unknown-linux-gnu > gcc -v Reading specs from /usr/local/lib/gcc/x86_64-unknown-linux-gnu/3.4.5/specs Configured with: ../gcc-3.4.5/configure Thread model: posix gcc version 3.4.5 Distribution: SUSE LINUX 10.0 (X86-64) > uname -srv Linux 2.6.13-15.7-default #1 Tue Nov 29

Successful build and install of gcc 3.4.5

config.guess output: i686-pc-linux-gnu gcc -v output: Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.5/specs Configured with: ../gcc-3.4.5/configure Thread model: posix gcc version 3.4.5 Distribution: SUSE LINUX 10.0 (i586) uname -srv output:Linux 2.6.13-15.7-default #1 Tue Nov 29 1

Successful Build: gcc-4.1-20051230 i686-pc-mingw32

E:\msys\1.0\home\gcc>gcc -v Using built-in specs. Target: mingw32 Configured with: ../gcc-4.1-20051223/configure --host=mingw32 --build=mingw32 -- target=mingw32 --enable-threads --disable-nls --enable-optimize --enable-languag es=c,c++ --prefix=e:/mingw4 Thread model: win32 gcc version 4.1.0 20051

Successful build of gcc 3.3.4

Hi all. Just reporting a successful build of GCC version 3.3.4 for the full GCC bundle on a platform not listed in your build stats. Note that this exact version is of special interest, since it is the required release for development of Maya plugins (see http://www.alias.com/eng/support/maya

Successful build of gcc 4.0.2 on alphaev56-dec-osf5.1b (c, c++, treelang)

Dear list, # gcc -v Using built-in specs. Target: alphaev56-dec-osf5.1b Configured with: ../configure --enable-threads=posix --enable-languages=c,c++,treelang --prefix=/usr/local --enable-version-specific-runtime-libs --enable-shared --enable-nls --enable-interpreter Thread model: posix g

Re: GCC 4.0.2 Released (successful build)

Hello again! Okay, gcc-4.0.2 built just fine on an embedded mpc8540 (ppc, e500, SPE extension): $ ./gcc -v Using built-in specs. Target: powerpc-unknown-linux-gnu Configured with: ../gcc-4.0.2/configure --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-languages=c,c++,objc

Successful Build and Installation of GCC

> Output from running srcdir/config.guess. Do not send that file itself, just the one-line output from running it. i586-pc-linux-gnu > The output of gcc -v for your newly installed gcc. This tells us which version of GCC you built and the options you passed to configure. Using built-in specs

Successful build off gcc-3.4.4 on Mac OS X 10.2.8

Not that it come as a big surprise, but I successfully compiled gcc-3.4.4 on darwin 6.8 (as specified by uname -a) config.guess reports powerpc-apple-darwin.6.8 gcc -v reports Configured with ../gcc-3.4.4/configure --program-suffix=-3.4.4 --enable-languages=c,c++,f77,java,objc Thread model: p

successful build and install gcc 3.4.4

772: config.guess i686-pc-linux-gnu 778: ../bin/gcc -v Reading specs from /home/projects/nisac/current-third-party/lib/gcc/i686-pc-linux-gnu/3.4.4/specs Configured with: ./configure --prefix=/home/projects/nisac/current-third-party --x-includes=/usr/X11R6/include --x-lib=/usr/X11R6/lib Thread mod

successful build of gcc 4.0.1 on Mac OSX 10.2.8

% ../gcc-4.0.1/config.guess powerpc-apple-darwin6.8 % /usr/local/bin/g++-4.0.1 -v Using built-in specs. Target: powerpc-apple-darwin6.8 Configured with: ../gcc-4.0.1/configure --program-suffix=-4.0.1 --enable-languages=c,c++ --enable-threads=posix : (reconfigured) ../gcc-4.0.1/configure --program-

successful build of gcc 4.0.1 on i686-pc-cygwin, cohexist with gcc 3.4.1

/gcc/4.0/gcc-4.0.1/config.guess i686-pc-cygwin $ /work/install/bin/gcc -v Using built-in specs. Target: i686-pc-cygwin Configured with: /gcc/4.0/gcc-4.0.1/configure --verbose --prefix=/work/install --exec-prefix=/work/install --sysconfdir=/work/i nstall/etc --libdir=/work/install/lib --libexecdir=

GCC 4.0.1 RC1 successful build

GCC 4.0.1 was successfully built on Fedora Core 3 using 3.4.4 as the starting compiler. [EMAIL PROTECTED] opt2]$ gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../configure --prefix=/opt2/gcc401 --enable-threads=posix --with-system-zlib -enable-shared --enable-__cxa_atexit

successful build of GCC 4.0.0 on Mac OS 10.4.1

gcc-4.0.0 -v Using built-in specs. Target: powerpc-apple-darwin8.1.0 Configured with: ../gcc-4.0.0/configure --program-suffix=-4.0.0 --enable-languages=c,c++,objc,java Thread model: posix gcc version 4.0.0 ./config.guess powerpc-apple-darwin8.1.0 uname -a Darwin Bojan-Antonovics-Computer.loca

Re: successful build on i686-pc-cygwin

Christopher Faylor wrote: >On Sat, May 07, 2005 at 04:44:44PM +0100, Dave Korn wrote: > > >>Original Message >> >> >>>From: J?rgen Havsberg Seland >>>Sent: 06 May 2005 23:30 >>> >>> >>>additional information: Important to mount all binary folders with the >>>-X option, as other

Re: successful build on i686-pc-cygwin

On Sat, May 07, 2005 at 04:44:44PM +0100, Dave Korn wrote: >Original Message >>From: J?rgen Havsberg Seland >>Sent: 06 May 2005 23:30 > >>additional information: Important to mount all binary folders with the >>-X option, as otherwise command-lines will be too long, for instance: >> >>mount

RE: successful build on i686-pc-cygwin

Original Message >From: Jørgen Havsberg Seland >Sent: 06 May 2005 23:30 > additional information: > Important to mount all binary folders with the -X option, as otherwise > command-lines will be too long, for instance: > >mount -f -X c:/cygwin/bin /bin > > Important: This also goes

successful build on i686-pc-cygwin

srcdir/config.guess: i686-pc-cygwin gcc -v: Using built-in specs. Target: i686-pc-cygwin Configured with: ../gcc-4.0.0/configure --verbose --prefix=/work/install --exec-prefix=/work/install --sysconfdir=/work/ install/etc --libdir=/work/install/lib --libexecdir=/work/install/lib --mandir=/work/in

successful build of GCC 4.0.0 on Mac OS 10.3.9 (bootstrap, only C)

Note: - I could build GCC 4.0.0 only with Fortran95 and C. - with C++ and Java building failed. - I will try to build GCC 4.0 with itself, now with (nearly) all languages. gcc -v Using built-in specs. Target: powerpc-apple-darwin7.9.0 Configured with: ../gcc-4.0.0/configure --program-suffix=-4.0.0c

successful build of GCC 4.0.0 on Mac OS 10.3.9 (bootstrap, Fortran95)

Note: - I builded GMP 4.1.4 with MPFR 4.1 myself. - I switched to GNU make and actualized some other tools as avalable (http://gcc.gnu.org/install/prerequisites.html). - Building fails if standard tools from Mac OS 10.3.9 are used! The prerequisits changed! - Other languages will come later. /us

Successful Build Report for GCC 4.0.0 C and C++

Hello! Here is a report of a successful build of GCC 4.0.0's C and C++ compilers on a RedHat 9 system. [Report starts here.] Basic information:- 'config.guess': i686-pc-linux-gnu 'gcc -v' (actual command was 'gcc-4 -v'): Using built-in specs. Target: i686-pc-linu

GCC 4.0.0: (mostly) successful build and installation on GNU/Linux PowerPC

This is the information requested in INSTALL/finalinstall.html: Output of config.guess: powerpc-unknown-linux-gnu Output of gcc-4.0.0 -v: Using built-in specs. Target: powerpc-unknown-linux-gnu Configured with: ../gcc-4.0.0/configure --enable-threads=posix --with-cpu=750 --enable-languages=c,c++,j

One fully and one partially successful build

Successful build: $ which as; as --version /phil/sw/sunos/sparc/bin/as GNU assembler 2.15.97 20050420 Copyright 2005 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely

gcc 4.0.0 successful build

Hi, finally, gcc 4.0.0 is released and it builds on IRIX 6.3 (as opposed to my numerous failing tries of gcc 3.x.y). lucy 70% ./gcc-4.0.0/config.guess mips-sgi-irix6.3 lucy 71% /usr/gcc-4.0/bin/gcc -v Using built-in specs. Target: mips-sgi-irix6.3 Configured with: /usr/people/eblachut/dev/gcc-4.

Successful build of gcc-3.4.3 Red Hat 8.0, Kernel 2.6.11.2

Reporting a smooth and successful build of gcc-3.4.3 on Red Hat Linux release 8.0 (Psyche) with kernel 2.6.11.2 [EMAIL PROTECTED] gcc-3.4.3]# ./config.guess i686-pc-linux-gnu [EMAIL PROTECTED] gcc-3.4.3]# gcc -v Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.3/specs Configured with

Gcc successful build

I have successfully built GCC-3.4.3 on the alpha-unknown-linux-gnu platform. The specific OS is gentoo linux 2004.3 on the ev56 alpha platform. My glibc is version 2.3.2. The specific version portage emerged is "gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7

Successful build of 3.4.3

I successfully built gcc-3.4.3 on SuSE Linux 9.2: Here is the relevant information: config.guess: i686-pc-linux-gnu gcc -v: Reading specs from /opt/gcc-3.4.3/lib/gcc/i686-pc-linux-gnu/3.4.3/specs Configured with: ../gcc-3.4.3/configure --prefix=/opt/gcc-3.4.3 Thread model: posix gcc version 3.4.

Mostly successful build and install

./config.guess i686-pc-linux-gnu gcc -v Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.3/specs Configured with: /Data/MyDownloads/gcc-3.4.3/configure Thread model: posix gcc version 3.4.3 languages enabled all /etc/issue Red Hat Enterprise Linux WS release 3 (Taroon Update 4) uname -a