[Proj] library name not libproj.so.0 anymore?
Peter S Galbraith
psg at debian.org
Mon Jul 26 11:14:55 EDT 2004
> Frank Warmerdam <warmerdam at pobox.com> wrote:
> > Peter S Galbraith wrote:
> > > Hi all,
> > > Building proj creates:
> > > /usr/lib/libproj.0
> > > /usr/lib/libproj.0.4.2
> > > instead of libproj.so.0 and libproj.so.0.4.2 as it used to.
> > > Is this intentional?
> > > (Unfortunately, I uploaded a package to Debian like this without
> > > noticing it.)
> > Peter,
> > I have not encountered this problem doing a default build and install.
> > Are the files in your src/.libs directory named the same way? I wonder
> > what is going on.
> It happenned after I ran autoreconf.
For future reference, this happened when I ran autoreconf with libtool
verion 1.5 against your 1.4 version files. Installing version 1.4 on my
build system fixed the problem.
> Instead, I now simply used recent
> config.guess and config.sub files.
And I still needed to do that for mipsel support. You may consider
updating your config.guess and config.sub files too.
More information about the Proj