Hi Dave,
Thanks for your reply, and particularly the suggestion that i check
out mac****ts, which i intend to do.
Now, i've used fink on a prior mac, and the fink people have indeed
made a huge variety of software available for pretty easy use on
the mac.
But i have two reasons to see how far i can get without using fink
this time around:
(1) The fink packages require admin access to install, so they change
the global nature of the machine. It is not possible for each user
of
the machine to have a different view of /sw (the root of most of
fink).
I understand that the authors may have been more or less forced into
this kind of design, at least partially, because of the nature of x-
windows,
for example. And installing everything in /sw makes the framework
much simpler, and thus much more robust. So, they have good reasons
for doing it the way the way they do, but i want my installation
of gcc to be entirely unprivileged.
(2) gcc has an elaborate configuration process that accommodates a
vast range of hardware and operating systems. It should be possible
to build anywhere, with the configuration phase catching any
potential problems. Now the reality may not be so good, but i
would at least like to find out how far it is from the ideal.
Thanks again for your mail and advice, and if you are anybody
else has any further suggestions, i'm all ears.
dan
On Jun 1, 5:15 am, Dave Seaman <dsea...@[EMAIL PROTECTED]
> wrote:
> On Thu, 31 May 2007 23:01:11 -0700, dan wrote:
> > Hi All,
> > I attempted to compile gcc 4.2.0 on an intel mac.
> > The OS is 10.4.9, and everything is standard (no fink, no extra
> > installed software of any kind).
> > I configured the software with no extra options (except an install
> > path).
> > After producing around 30,000 lines of output, the compilation process
> > errors out in stage 3, with a long command that starts off .......bld/
> > 0/./gcc/xgcc -shared-libgcc........ and ends up .......-
> > compatibility_version 9 -current_version 9.0, followed by the message
> > /usr/bin/libtool: fatal error in ld64
> > This is 5 layers deep in the make (libgcj.la).
> > Thanks in advance for any clues on how to deal with this.
>
> You said you are not using fink, but that seems to be the simplest
> solution to the problem. I have gcc 4.2 on my Intel Mac, installed via
> fink.
>
> Mac****ts appears to have it also, though I haven't tried that route.
>
> --
> Dave Seaman
> Oral Arguments in Mumia Abu-Jamal Case heard May 17
> U.S. Court of Appeals, Third Circuit
> <http://www.abu-jamal-news.com/>
|
