[Dev] Tiger switch test?
Grant Baillie
grant at osafoundation.org
Wed May 4 09:29:35 PDT 2005
On May 3, 2005, at 9:45 PM, Andi Vajda wrote:
>> Well, I tried a full build, but didn't get past persistence/db:
>>
>> /usr/bin/libtool: for architecture: cputype (16777234) cpusubtype
>> (0) file: -lSystem is not an object file (not allowed in a library)
>> make[2]: *** [libdb-4.3.la] Error 1
>> make[1]: *** [build] Error 2
>> make: *** [persistence/db] Error 2
>>
>>
>
> Seems to build fine for me. Here is what I did:
> - installed Tiger on a firewire drive, with a 'scratch' install
> - booted from it
> - installed Tiger dev tools included on the DVD, omitting gcc 3.3
> (only gcc
> 4.0 got installed)
> - fixed the links in /usr/bin that make gcc/g++/cc/c++ point to an
> inexistant gcc 3.3 toolchain to point to the gcc 4.0 one
> - checked out a new osaf tree
> - cd external/persistence/db
> - make
> it built fine, without anything unusual
>
> I didn't do a full chandler build yet. I'm still building gcj from
> the most recent gcc 4.1 snapshot. For that, I also had to fix
> another bogus link in /usr/include: /usr/include/stdint.h needs to
> point at gcc/darwin/4.0/stdint.h
> instead of gcc/darwin/default/stdint.h
Of course, it's a bug that installing gcc 4 left you with broken
symlinks. I think /usr/bin/gcc_select would probably have helped with
some of the symlink munging (assuming it actually would have worked,
since your config was clearly in a mixed quantum state).
--Grant
More information about the Dev
mailing list