Hi,
I think this is either an automake problem or a libtool problem, (or
maybe even a glibc problem) so cc'ing both lists. Please cc me on
replies. My apologies in advance to those subscribed to both lists :)
Far too many times, I have run ./configure && make && sudo make install
on a new piece
Bob Friesenhahn wrote:
>
> Your email seems to contain a lot of details, but upon closer
> inspection the details are not of the right type. For example, you
> have not even identified the operating system you are using.
>
Sorry, it's i686-pc-linux-gnu, Slackware 12.0 (mostly).
$ uname -a
Laurence Darby wrote:
> Alright, for reproducibility, here is a small example,
> inotify-tools-3.12.tar.gz. Firstly please run
>
> # locate libinotifytools.so | xargs rm
>
> so there is zero chance of hiding the error with stale libraries
> hiding somewhere on the sys
Bob Friesenhahn wrote:
> > I thought it did, but this isn't a linking problem (as
> > in /usr/bin/ld). The problem is loading a program at start up time
> > (when loading dynamic linked libraries).
> >
> > It's only when a package builds its own libs which it dynamic links
> > to runtime, which is
Ralf Wildenhues wrote:
> [ http://thread.gmane.org/gmane.comp.gnu.libtool.general/8726 ]
>
> Hello Laurence,
>
Hi Ralf, thanks for looking at this!
I'll admit it's not very serious, another one of my nitpicks :)
> Apologies for the delay, and apologies again for not citing better,
uh? gmane
