Gerald,
Thanks (late) for the patch. I have some new questions:
(1) I get the following errors:
ERROR: can't read "HOSTCC": no such variable
while executing
"remote_exec host "$HOSTCC $HOSTCFLAGS $generator_cmd""
invoked from within
"set status [remote_exec host "$HOSTCC $HOSTCFLAGS $gen
"Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes:
> This is the project proposal that I am planning to submit to Google
> Summer of Code 2007. It is based on previous work of Jeffrey Laws,
> Diego Novillo and others. I hope someone will find it interesting and
> perhaps would like to act as mentor
Manuel López-Ibáñez wrote:
This is the project proposal that I am planning to submit to Google
Summer of Code 2007. It is based on previous work of Jeffrey Laws,
Diego Novillo and others. I hope someone will find it interesting and
perhaps would like to act as mentor. Feedback is very welcome (ev
I have obtained the same error on my ppc64 yellow dog linux:
/bin/sh ./libtool --mode=compile
/home/victork/mainline-vanila/build/./gcc/gfortran
-B/home/victork/mainline-vanila/build/./gcc/
-B/home/victork/mainline-vanila/usr/ppc64-yellowdog-linux/bin/
-B/home/victork/mainline-vanila/usr/ppc64-y
On 3/18/07, Victor Kaplansky <[EMAIL PROTECTED]> wrote:
I have obtained the same error on my ppc64 yellow dog linux:
collect2: ld terminated with signal 11 [Segmentation fault]
> I get the following error on PPC while bootstrapping mainline.
> Re-runing make I get:
> collect2: ld terminated
Is there a convenient switch to make GCC bootstrap on Debian/amd64
without patching the build infrastructure? Apparently, GCC tries to
build 32-bit variants of all libraries (using -m32), but the new
compiler uses the 64-bit libc instead of the 32-bit libc, hence
building them fails.
I don't need
On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
I don't need the 32-bit libraries, so disabling their compilation
would be fine. --enable-targets at configure time might do the trick,
but I don't know what arguments are accepted.
Would --disable-multilib work?
Gr.
Steven
* Steven Bosscher:
> On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
>> I don't need the 32-bit libraries, so disabling their compilation
>> would be fine. --enable-targets at configure time might do the trick,
>> but I don't know what arguments are accepted.
>
> Would --disable-multilib wor
On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
I'll try, but I doubt it. According to the installation
documentation, amd64 is not a multilib target.
HUH??? Which documentation? x86_64 for GCC is a multilib target and
has been since day 1 IIRC.
-- Pinski
* Andrew Pinski:
> On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
>>
>> I'll try, but I doubt it. According to the installation
>> documentation, amd64 is not a multilib target.
>
> HUH??? Which documentation?
I misinterpreted the installation manual, sorry. I thought that all
the multil
> For example, this AC_LIBTOOL_WIN32_DLL macro was
> removed/deprecated from libtool three years ago.
What should be used with a recent libtool? And where is it documented?
There is no need for any special consideration to create a DLL with
modern libtool. One just needs --enable-shared at con
Under cygwin, I get a stage 2 and 3 comparison failure that's not
supposed to be there...
Comparing stages 2 and 3
warning: ./cc1-checksum.o differs
warning: ./cc1obj-checksum.o differs
warning: ./cc1objplus-checksum.o differs
warning: ./cc1plus-checksum.o differs
warning: ./libgcc/_chkstk.o diff
I am a seeing the following warnings in the initial
bootstrap of gcc 4.2.0 RC1 on powerpc-apple-darwin8...
gcc -c -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wmissing-format-attribute -pedantic -Wno-long-long
-DHAVE_CONFIG_H -I. -I../../.
Thanks for the help.
But my problem is not yet solved
I created a new folder , configured with
--prefix= --disable-bootstrap --enable-languages=c
option and then did a
make
but the newly built compiler is still used in the build process. i.e
in the generated
Makefile
CC_FOR_TAR
> How can I get the build scripts to use the precompiled gcc throughout
> the build process ?
Short answer is you can't. The newly build gcc is always used to build the
target libraries[1].
Paul
[1] Except when building a Canadian cross, in which case you're expected to
have a build->target cr
As part of adding a new pass to GCC I am intercepting addition to and
subtraction from pointers. These are represented by PLUS_EXPR and
MINUS_EXPR tree nodes. I need to be able to find out which of the node's
two operands is the actual pointer and which is the integer that has been
added to it.
On 3/18/07, Alexander Lamaison <[EMAIL PROTECTED]> wrote:
As part of adding a new pass to GCC I am intercepting addition to and
subtraction from pointers. These are represented by PLUS_EXPR and
MINUS_EXPR tree nodes. I need to be able to find out which of the node's
two operands is the actual p
On Mar 18, 2007, at 2:55 PM, Karthikeyan M wrote:
my problem is not yet solved
It is, it doesn't bootstrap.
../../../gcc-4.2.0-20070316/fixincludes/fixincl.x:7597: warning:
string length '575' is greater than the length '509' ISO C89
compilers are required to support
Are these expected?
Yup.
-eric
Paul Brook wrote:
How can I get the build scripts to use the precompiled gcc throughout
the build process ?
Short answer is you can't. The newly build gcc is always used to build the
target libraries.
Nice statement but what does this really mean?
Does this for instance mean that: "T
Kai Ruottu wrote:
Paul Brook wrote:
How can I get the build scripts to use the precompiled gcc throughout
the build process ?
Short answer is you can't. The newly build gcc is always used to build the
target libraries.
Nice statement but what does this really mean?
Does this for ins
On Sat, 2007-03-17 at 18:28 +, Manuel López-Ibáñez wrote:
> This is the project proposal that I am planning to submit to Google
> Summer of Code 2007. It is based on previous work of Jeffrey Laws,
> Diego Novillo and others. I hope someone will find it interesting and
> perhaps would like to ac
Florian Weimer <[EMAIL PROTECTED]> writes:
> * Steven Bosscher:
>
>> On 3/18/07, Florian Weimer <[EMAIL PROTECTED]> wrote:
>>> I don't need the 32-bit libraries, so disabling their compilation
>>> would be fine. --enable-targets at configure time might do the trick,
>>> but I don't know what argum
23 matches
Mail list logo
