On Sat, Jan 12, 2008 at 08:21:38AM +0100, Kai Wang wrote: > The recommended way is: (for now) > > 1. Backup your GNU ar first: > % cp /usr/bin/ar SOME_BACKUP_DIR > > 2. Build BSD ar > extract the tarball > % cd ar > % make > > 3. Replace > # cp ./ar /usr/bin/ar > # cd /usr/bin > # ln -f ar ranlib > > Then you can do something like ports build or "make buildworld" > to try it out. > > Later when you need to recover GNU ar: > > # cp SOME_BACKUP_DIR/ar /usr/bin/ar > # cd /usr/bin > # ln -f ar ranlib This won't work as GNU ranlib is not merely a hardlink to ar. Thus correct way would be: 1. Backup your GNU ar and ranlib first: % cp /usr/bin/ar SOME_BACKUP_DIR % cp /usr/bin/ranlib SOME_BACKUP_DIR 2. Build BSD ar extract the tarball % cd ar % make 3. Replace # cp ./ar /usr/bin/ar # cd /usr/bin # ln -f ar ranlib When recover GNU ar: # cp SOME_BACKUP_DIR/ar /usr/bin/ar # cp SOME_BACKUP_DIR/ranlib /usr/bin/ranlib Sorry for the mess... BTW: I'm working on a patch for -CURRENT as peter_at_ just suggested.Received on Sat Jan 12 2008 - 07:51:36 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:25 UTC