Hi mentors,
That's not the unusual way to link to a shared library. You should use
something like:
$(CC) -g -o hello hello.o -L../lib/ -lsharedlib
(Although it would probably only work if the library had a SONAME.)
I did an experiment. Had the rpath issue fixed, the build result
On Fri, Jun 12, 2015 at 08:11:14AM +, lumin wrote:
hello: hello.o
$(CC) -g -o hello hello.o ../lib/libsharedlib.so --NOTICE
That's not the unusual way to link to a shared library. You should use
something like:
$(CC) -g -o hello hello.o -L../lib/
Hi mentors,
I've been struggling with this shared library linking issue for
a while.
I scanned maint-guide, dev-ref (detail not enough),
debmake-doc (osamu's new version of maint-guide),
and a library packaging guide [1] that debmake-doc recommended.
Then I still have no idea how to handle the
On Fri, Jun 12, 2015 at 08:11:14AM +, lumin wrote:
And I'd like to package it as following:
package: hello
depends: libsharedlib1
package: libsharedlib1
NOTE: libsharedlib1 has no SONAME
If it has no SONAME then this won't work. Shared libraries
On Fri, Jun 12, 2015 at 03:16:00PM +, lumin wrote:
NOTE: libsharedlib1 has no SONAME
If it has no SONAME then this won't work. Shared libraries should have
SONAMEs (also, where that 1 does come from then?).
Well, upstream doesn't set SONAME, and ..
All public shared libs must
lumin cdlumin...@gmail.com writes:
Is there any problem with -rpath that needs a fix ?
https://wiki.debian.org/RpathIssue
--
Feri.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hi Andrey Rahmatullin,
NOTE: libsharedlib1 has no SONAME
If it has no SONAME then this won't work. Shared libraries should have
SONAMEs (also, where that 1 does come from then?).
Well, upstream doesn't set SONAME, and ..
if I just put .so libs together with executables into into a
7 matches
Mail list logo
