On 10/18/13 01:28, M. Fioretti wrote:
On Thu, Oct 17, 2013 12:33:31 PM -0500, Kevin Martin wrote:
>>
> Hmm, I don't even have that 19626 file in .libs. The entirety of my .libs
directory is:
>
> -rwxrwxr-x 1 500 1000 47055 Oct 17 10:48 abiword
> lrwxrwxrwx 1 500 1000 20 Oct 17 10:48 libabiword-3.0.la ->
../libabiword-3.0.la
> -rw-rw-r-- 1 500 1000 1200 Oct 17 10:48 libabiword-3.0.lai
> -rwxrwxr-x 1 500 1000 51656791 Oct 17 10:48 libabiword-3.0.so
> -rw-rw-r-- 1 500 1000 28232 Oct 17 10:48 libabiword_3.0_la-abi_ver.o
> -rw-rw-r-- 1 500 1000 72024 Oct 17 10:48 libabiword_3.0_la-libabiword.o
> -rwxrwxr-x 1 500 1000 47055 Oct 17 10:49 lt-abiword
>
>
> Did you compile as root or sudo by any chance?
yes, I compiled as root (I didn't even realize it when I started: I
had just been doing upgrades and other "root" stuff", then continued
to work in the same terminal...)
anyway, after running that abiword wrapper once as root as reported yesterday:
- my .libs folder is the same as yours (no 19626 file anymore)
- now I can run the wrapper (getting "Abiword 3.0.0") in the about box
even as normal user
at this point, what I would like to know is why make and "make
install" left me with a brand new binary of the old version (2.8.6) in
/usr/local/bin/ and a wrapper for the right version in the _wrong_
place. Even if I should not have ran make as root, why should
something like this happen?
Confused,
Marco
So if you redo your "make install" does the binary change in
/usr/local/bin?
Kevin