I'm trying to build a 64-bit mainline compiler on powerpc-darwin; I
want gcc to generate 32-bit binaries by default, I just want cc1,
etc., to be 64-bit binaries so I can compile large files.
This works in 4.1, but not on mainline. This is reported at
http://gcc.gnu.org/bugzilla/show_bug.cg
Snapshot gcc-4.2-20060415 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20060415/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.2 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
On Apr 13, 2006, at 8:21 AM, Diego Novillo wrote:
either remove the line or convert it to VEC somehow.
Remove it. It's now done with NUM_REFERENCES which just uses
common.aux. Dan probably forgot to remove it when he converted it.
Guilty as charged.
I usually let "unused variable " war
$ cd ~/archives/gcc/src/gcc-4.0.3
$ ./config.guess
i686-pc-cygwin
$ /usr/local/bin/gcc -v
Using built-in specs.
Target: i686-pc-cygwin
Configured with: /home/gob/archives/gcc/src/gcc-4.0.3/configure
--enable-languages=c++ --enable-win32-registry
Thread model: single
gcc version 4.0.3
$
What I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Murphy wrote:
> Ranjit Mathew wrote:
>>
>> However, when I moved the binaries to another machine
>> where MinGW was installed in "D:\MinGW", the compiler was
>> not able to find the C runtime headers, even though the
>> folder structure was exactl
H. J. Lu wrote:
It may be related to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435
Can you try
http://gcc.gnu.org/ml/gcc-patches/2006-01/msg01757.html
Tried that but no difference.
I had a look through gcc.c and noticed that standard_exec_prefix and
standard_libexec_prefix are constants
