--- Comment #13 from ebotcazou at gcc dot gnu dot org 2010-01-11 11:30
---
I think we should consider that x86_64-apple-darwin is not supported in 4.4 and
make sure that it will be in 4.5, in particular fix PR middle-end/42068.
--
ebotcazou at gcc dot gnu dot org changed:
--- Comment #14 from simon at pushface dot org 2010-01-11 21:35 ---
Concur with Eric.
Um, I could submit a patch for PR middle-end/42068 if it would help? Not aware
of procedure here.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42518
--- Comment #15 from ebotcazou at gcc dot gnu dot org 2010-01-11 21:41
---
Um, I could submit a patch for PR middle-end/42068 if it would help? Not aware
of procedure here.
You'd need to go through the full testing procedure described here:
http://gcc.gnu.org/contribute.html
--
--- Comment #12 from simon at pushface dot org 2009-12-31 16:25 ---
I have tried gcc-4_4-branch and indeed it correctly identifies the triplet
without any help (I have been having some trouble with exactly what compiler I
am configuring with).
The problem turns out to be in
--- Comment #10 from simon at pushface dot org 2009-12-30 18:29 ---
I've done as Eric suggests in #8 (though it looks to me as though the build
system is very close to supporting just --build= in this case!).
Situation now is that something in gcc/ada/gcc-interface/Makefile is selecting
--- Comment #11 from howarth at nitro dot med dot uc dot edu 2009-12-30
20:50 ---
Please try an svn pull of current gcc-4_4-branch. Assuming that you have EMT64
capable hardware and want to build the native x86_64 version of the FSF gcc
compilers, the new config.guess should properly
--- Comment #1 from simon at pushface dot org 2009-12-29 15:01 ---
Get a similar failure building GCC 4.3.3:
/Users/simon/gcc-build-4.3.3-x86_64/./gcc/xgcc
-B/Users/simon/gcc-build-4.3.3-x86_64/./gcc/
-B/opt/gcc-4.3.3-x86_64/x86_64-apple-darwin10.2.0/bin/
--- Comment #2 from ebotcazou at gcc dot gnu dot org 2009-12-29 15:24
---
There is something strange: the report is about a native i386 compiler built on
x86-64 but the configure line is for a native x86-64 compiler. Which one is
correct? Does the base compiler target i386 or x86-64?
--- Comment #3 from simon at pushface dot org 2009-12-29 18:06 ---
Sorry if I've caused confusion by misunderstanding the reporting system.
I can build GCC4.4.2[i386-apple-darwin10.2.0] using
GNAT-GPL-2009[i386-apple-darwin10.2.0].
I then try to build
--- Comment #4 from howarth at nitro dot med dot uc dot edu 2009-12-29
18:25 ---
Are you building on a Core Duo (ie non-EMT64 capable) machine? If not, the
default code generation of the Apple system compiler should be to execute and
generate x86_64 code under 10.6. You can't take the
--- Comment #5 from howarth at nitro dot med dot uc dot edu 2009-12-29
18:32 ---
You might try current gcc 4.4.2 branch. It contains the latest config.guess
which determines the architecture type according to the system compiler's
default code generation for intel darwin.
--
--- Comment #6 from howarth at nitro dot med dot uc dot edu 2009-12-29
18:33 ---
I meant gcc-4_4-branch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42518
--- Comment #7 from simon at pushface dot org 2009-12-29 18:48 ---
I think the immediate cause is that the alignment for generated tagged type
support objects (see eg exp_disp.adb:4007) is derived from that of
System.Storage_Elements.Integer_Address (defined as mod Memory_Size) which
--- Comment #8 from ebotcazou at gcc dot gnu dot org 2009-12-29 19:29
---
I then try to build GCC4.4.2[x86_64-apple-darwin10.2.0] using
GCC4.4.2[i386-apple-darwin10.2.0], with the reported results.
[...]
I've been using --build=x86_64-apple-darwin10.2.0 to indicate that I want to
--- Comment #9 from howarth at nitro dot med dot uc dot edu 2009-12-29
23:37 ---
(In reply to comment #8)
--build=xxx means you're using a xxx compiler to build. Since you apparently
don't have a x86_64 compiler at hand but only a i386, you cannot do that.
You first need to build
15 matches
Mail list logo
