On Monday, June 2, 2003, at 01:48 PM, Bill Northcott wrote:
Because of the way things are set up, adding fsf gcc support is
essentially adding a completely different compiler. Depending on my
available free time, I may decide to revisit this issue, do you
really think it is required?
With stock G
> >> Because of the way things are set up, adding fsf gcc support is
> >> essentially adding a completely different compiler. Depending on my
> >> available free time, I may decide to revisit this issue, do you
> >> really think it is required?
> >
> > With stock GCC 3.3, most if not all of the App
On Saturday, May 31, 2003, at 11:54 PM, Marcus G. Daniels wrote:
Peter O'Gorman wrote:
Because of the way things are set up, adding fsf gcc support is
essentially adding a completely different compiler. Depending on my
available free time, I may decide to revisit this issue, do you
really thi
Peter O'Gorman wrote:
Because of the way things are set up, adding fsf gcc support is
essentially adding a completely different compiler. Depending on my
available free time, I may decide to revisit this issue, do you really
think it is required?
With stock GCC 3.3, most if not all of the Apple
Well, the FSF gcc is explicitly not supported, that is why the check
for Apple.
I assumed (obviously wrongly) that you were using Apple's gcc-3.3 from
darwin cvs 1314
Because of the way things are set up, adding fsf gcc support is
essentially adding a completely different compiler. Depending on
Another member of our group suggested:
> Before installing libtool 1.5, go through the libtool.m4 and change all
> the stuff
> that says:
> if $CC -v 2>&1 | grep 'Apple' >/dev/null ; then \
> to:
> if true; then
> Then rerun libtool's `bootstrap', and reisntall.
> The basic problem is that libtool
Could you possible run this again in this directory (preferably with
all the .o's present in the .libs dir) using `"make SHELL=/bin/sh -x"
>& log.txt' and send me the log.
Thanks,
Peter
On Friday, May 30, 2003, at 01:34 PM, Bill Northcott wrote:
*** libtool 1.5*
