Bug in fsf gcc-3.3

Subject: Bug in fsf gcc-3.3
From: "Peter O'Gorman" <email@hidden>
Date: Sun, 1 Jun 2003 22:20:11 +0900

Hi,
Just been trying to get fsf gcc-3.3 release to play nice with libtool, all the linker options are finally passed through, great!

The problem:
/usr/local/bin/gcc -bundle
gcc: couldn't run `/usr/local/bin/undle-gcc-3.3': No such file or directory

If -bundle is the first argument to gcc, it tries to exec the correct gcc for the specified machine, in this case "undle" :)

It works fine if it is not the first argument, but it took me a while to figure that out.

Another issue is __private_extern__ is not understood by fsf gcc, so any code which #include's mach-o/dyld.h can not be compiled. Probably, in this case, the header should be fixed rather than the compiler.

Great work on the 3.3 release,
Thanks,
Peter
_______________________________________________
darwin-development mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-development
Do not post admin requests to the list. They will be ignored.

Next by Date: Re: Min HFS+ size 512 bytes vs standard 4kb size
Next by thread: Re: Min HFS+ size 512 bytes vs standard 4kb size
Index(es):
- Date
- Thread

Home