Since you are linking directories, using "ln -sf <source> <dest>" rather
than "ln -s <source> <dest>" should fix it nicely.  The "-f" option
forces an overwrite of the existing symbolic link.

Jeff Raven wrote:
> 
> On Fri, May 26, 2000 at 10:23:59AM +0100, Jonathan Irving wrote:
> > heya
> >
> > compiling 0.60.3 on solaris 7, gcc 2.95.2, with a configure
> > of:
> >
> >   CXXFLAGS=-fpermissive ./configure --disable-styled-frames
> >
> > this happens:
> >
> > make[4]: Entering directory /usr/local/src/blackbox-0.60.3/nls'
> > ln: cannot create /usr/local/share/Blackbox/nls/POSIX/C: File exists
> > ln: cannot create /usr/local/share/Blackbox/nls/en_US/C: File exists
> > ln: cannot create /usr/local/share/Blackbox/nls/en/C: File exists
> > make[4]: *** [install-data-hook] Error 2
> > make[4]: Leaving directory /usr/local/src/blackbox-0.60.3/nls'
> > make[3]: *** [install-data-am] Error 2
> > make[3]: Leaving directory /usr/local/src/blackbox-0.60.3/nls'
> > make[2]: *** [install-am] Error 2
> > make[2]: Leaving directory /usr/local/src/blackbox-0.60.3/nls'
> > make[1]: *** [install-recursive] Error 1
> > make[1]: Leaving directory /usr/local/src/blackbox-0.60.3/nls'
> > make: *** [install-recursive] Error 1
> >
> 
> This occurs because you didn't uninstall the last version before
> installing this one, so when blackbox tries to create some
> symlinks for locales it fails because they aready exist. Other
> platforms don't seem to have this problem -- I guess their 'ln'
> isn't quite as picky.
> 
> Anyway, just cd /usr/local/share/Blackbox/nls, remove the existing
> symlinks, and run make install again. It should hopefully go
> through without a hitch.
> 
> Jeff Raven

-- 
***************************************************************
* Markland J. Benson          *                  IV&V Analyst *
* Azimuth, Inc.               *   NASA Software IV&V Facility *
* 100 University Drive        *         Phone: (304) 367-8364 *
* Fairmont, WV  26554         *           Fax: (304) 367-8221 *
***************************************************************

Reply via email to