On Mon, 2010-01-18 at 15:09 -0500, Stephen Bannasch wrote: > >On Mon, 2010-01-11 at 10:32 -0500, Stephen Bannasch wrote: > >> >I've never seen this error. What happens when you try to print the > >> >archive contents manually (with: ar t <archive>)? > >> > >> $ ar -t > >> java/src/bsd-port/build/bsd-i586/tmp/java/fdlibm/obj/libfdlibm.i586.a > >> k_standard.o > >> k_rem_pio2.o > >> k_cos.o > >> ... > > > >Search machines suggest to run ranlib(1) on the archive. You should > >probably ask on bsd-port-dev, people there should know more about Mac OS > >X build problems. Sorry. > > Thanks for that tip Christian. > > ar was not building the catalog file for the archive because the > environmental variable > COMMAND_MODE was set to 'legacy'. > > This occurred because I recently switched from the Mac OS X Terminal program > to iTerm because of iTerms much better handling ofcolored and styled fonts. > > Without another action COMMAND_MODElagacy when starting up a console shell on > Mac OS X using iTerm. > > I think most people use Terminal.app in Mac OS X so aren't affected by this > problem. > > In any case I updated my build script here: http://gist.github.com/243072 > > To change the COMMAND_MODE to unix2003 if it is set to legacy > > references: > http://old.nabble.com/Why-ar-doesn't-call-ranlib-on-Mac--td22319721.html
Cool you actually found out what the problem was. -- Christian _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
