From: Theodore A. R. <tr...@op...> - 2004-12-03 01:24:09
|
On Thu, 2 Dec 2004, Brian Dean wrote: > On Thu, Dec 02, 2004 at 04:52:07PM -0800, Theodore A. Roth wrote: > > > So I guess there's still that libiberty issue on OSX and Cygwin... > > At least on OSX, avarice linked fine against libiberty as installed by > gcc, so I did not run into any problems in that regard. Was that the > expected behaviour? I did not explicitly install libiberty from > binutils, only libbfd which was required for avarice. When building binutils and gcc from the tarballs, libiberty.a gets installed by both builds. There is no way that I found to stop this from happening (I beat me head against the wall for a few hours trying to figure how to do it with no success). It appears that the --enable-install-libiberty does do much. :-( The problem is API skew between the libiberty in binutils and that in gcc. --- Ted Roth PGP Key ID: 0x18F846E9 Jabber ID: tr...@ja... |