2012年2月27日16:21 Russ Allbery :
>>> This is a function that libtool normally performs if it is used properly.
>
>> I did: sudo make install
>
> Something needs to run libtool --mode=finish. I thought Automake normally
> arranged to run that at the end of make install. Is that not happening
> for
Miles Bader writes:
> 2012年2月27日9:41 Bob Friesenhahn :
>> This is a function that libtool normally performs if it is used properly.
> I did: sudo make install
> Is that not "using it properly"?
Something needs to run libtool --mode=finish. I thought Automake normally
arranged to run that at
2012年2月27日9:41 Bob Friesenhahn :
>> Just using the command: sudo ldconfig
>> after installing my package makes everything work!
>
> This is a function that libtool normally performs if it is used properly.
I did: sudo make install
Is that not "using it properly"?
-miles
--
Cat is power. Cat
On Mon, 27 Feb 2012, Miles Bader wrote:
Ok, the real problem seems to be that the system maintains a static
cache of _library files_ (not directories) for ld.so to use, and
simply adding a library doesn't update this cache.
Just using the command: sudo ldconfig
after installing my package make
2012年2月27日1:46 Peter Johansson :
>> I think it's desirable that it "just work" wherever it gets installed,
>> and no matter who installs it (e.g. prefix=$HOME should work, and
>> shouldn't require setting LD_LIBRARY_PATH).
>>
> In my case it did work with prefix=$HOME because in that case -rpath wa
Some output of a recent build of automake-1.10 - it requested I send it
to you!
Build is on OpenIndiana 151a2 (illumos/née OpenSolaris)
Regards, Lou Picciano
make[3]: `aclocal-1.10' is up to date.
make[3]: `automake-1.10' is up to date.
make[3]: Leaving directory
`/export/home/drlou/illumos-
Hello, all. In GRUB2 we have following problem: If
program_transform_name=s,grub,grub2 then
pkglibdir=$libdir/grub2 but pkgdatadir=$datadir/grub2
Is it intended or is it a bug? Is it likely to change in future versions?
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
On 2/26/12 11:31 PM, Miles Bader wrote:
I think it's desirable that it "just work" wherever it gets installed,
and no matter who installs it (e.g. prefix=$HOME should work, and
shouldn't require setting LD_LIBRARY_PATH).
In my case it did work with prefix=$HOME because in that case -rpath was
s
2012年2月27日0:58 Peter Johansson :
> On which system do you experience this? I've seen this problem on
> Fedora and the problem was that the linker search path and the dynamic
> loader search path were different. IIUC libtool sets -rpath if a used library
> is outside linker path.
Debian sid
I'm no
Hi Miles,
On 2/26/12 9:47 PM, Miles Bader wrote:
But ... it doesn't seem to. Is something broken, is there an option I
should set... or?
On which system do you experience this? I've seen this problem on Fedora
and the problem was that the linker search path and the dynamic loader
search path
On 02/26/2012 03:47 PM, Miles Bader wrote:
> I thought that as long as one used ".la" libraries, automake+libtool
> was supposed to handle all the grotty stuff like rpath automatically,
> adding -rpath $(libdir) if you depend on libraries installed to libdir
> and libdir isn't on the system library
I thought that as long as one used ".la" libraries, automake+libtool
was supposed to handle all the grotty stuff like rpath automatically,
adding -rpath $(libdir) if you depend on libraries installed to libdir
and libdir isn't on the system library search path. [Yeah, I also
know some people hate
12 matches
Mail list logo
