Opened 6 years ago

Closed 6 years ago

Last modified 3 years ago

#29104 closed defect (fixed)

GCC fails to build on Mac OS X Lion

Reported by: pbagwl@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.9.99
Keywords: lion Cc: egall@…
Port: gcc44

Description

As 1.9.2 .pkg fails to install ("you need snow leopard"), I've did SVN checkout, compiled macports and installed some of them. But when I tried to build GCC (4.3, 4.4, 4.5), it failed.

The error is:

:info:build checking for suffix of object files... configure: error: cannot compute suffix of object files: cannot compile

~ uname -a Darwin macbook 11.0.0 Darwin Kernel Version 11.0.0: Mon Mar 28 16:31:29 PDT 2011; root:xnu-1699.22.30~2/RELEASE_X86_64 x86_64

Attachments (4)

main.log (14.8 KB) - added by pbagwl@… 6 years ago.
config.log (29.4 KB) - added by pbagwl@… 6 years ago.
mail-llvm290.log (19.6 KB) - added by pbagwl@… 6 years ago.
patch-gcc46-xcode4.diff (404 bytes) - added by raimue (Rainer Müller) 5 years ago.
Use clang to bootstrap gcc

Download all attachments as: .zip

Change History (17)

Changed 6 years ago by pbagwl@…

comment:1 Changed 6 years ago by ryandesign (Ryan Schmidt)

  • Keywords mac os x 10.7 gcc build fail removed
  • Owner changed from macports-tickets@… to mww@…

It'll be difficult to fix Lion problems until we have access to it, which for most of us will be after Lion is released.

However, it might help if you attached the config.log.

Changed 6 years ago by pbagwl@…

comment:2 Changed 6 years ago by pbagwl@…

Lion uses XCode 4.1. Also I've found bug, that sounds pretty similar to mine - http://llvm.org/bugs/show_bug.cgi?id=9571

comment:3 Changed 6 years ago by pbagwl@…

I've installed llvm-gcc 2.9 into /Developer/usr/llvm-gcc-4.2 and now GCC build failed by another reason. Adding attachment.

Changed 6 years ago by pbagwl@…

comment:4 Changed 6 years ago by jmroot (Joshua Root)

  • Resolution set to wontfix
  • Status changed from new to closed
  1. We don't support prerelease OS versions
  2. We don't support using non-Apple toolchains
  3. NDA?

comment:5 Changed 6 years ago by pbagwl@…

jmr: OK, I got it, but just to mention:

We don't support using non-Apple toolchains

LLVM-GCC is official Apple toolchain, that is distributed with XCode. And it is default one.

comment:6 Changed 6 years ago by jmroot (Joshua Root)

If you built llvm-gcc from upstream sources that's not the same as what Apple ships in Xcode.

comment:7 Changed 6 years ago by pbagwl@…

No. I've used llvm-gcc from XCode 4.1 and created this ticket. And then I tried to use llvm-gcc 2.9 from upstream sources and added llvm290.log.

comment:8 Changed 5 years ago by bjornmagnus@…

Bump. I get it that this is unsupported, but in the very near future(I'm guessing less than a month) this is going to pose a problem to macports installations, so why tag it "wontfix" ? should be tagged "willhavetofixinamonth" :)

comment:9 Changed 5 years ago by raimue (Rainer Müller)

There is an upstream bug report.

comment:10 Changed 5 years ago by jeremyhu (Jeremy Huddleston Sequoia)

We should use clang to build gcc then

Changed 5 years ago by raimue (Rainer Müller)

Use clang to bootstrap gcc

comment:11 Changed 5 years ago by jeremyhu (Jeremy Huddleston Sequoia)

comment:12 Changed 5 years ago by jmroot (Joshua Root)

  • Resolution changed from wontfix to fixed

comment:13 Changed 3 years ago by egall@…

  • Cc egall@… added

Cc Me!

Note: See TracTickets for help on using tickets.