2013/1/8 Bryan Kadzban br...@kadzban.is-a-geek.net:
I *suppose* that might be because pkg-config or some equivalent fixes it
up somehow, pointing to the .la files directly. Or maybe -L affects
this somehow.
The -L option does have an effect on this.
--
Alexander E. Patrakov
]] Bryan Kadzban
Tollef Fog Heen wrote:
]] Tom Gundersen
This was what the old nss-myhostname did. Lennart: any good reason
to exclude the .la or should nss-myhostname be treated the same as
the other libs?
.la files are only useful for static linking.
Untrue. They're
2013/1/7 Bryan Kadzban br...@kadzban.is-a-geek.net:
Untrue. They're perfectly useful for dynamic linking as well:
http://www.sourceware.org/autobook/autobook/autobook_68.html#SEC68
Second paragraph. Also the page several sections after this one, about
installing a shared library with
On Sun, 06.01.13 10:46, Bryan Kadzban (br...@kadzban.is-a-geek.net) wrote:
Tollef Fog Heen wrote:
]] Tom Gundersen
This was what the old nss-myhostname did. Lennart: any good reason
to exclude the .la or should nss-myhostname be treated the same as
the other libs?
.la files are
On Sun, 06.01.13 02:16, Tom Gundersen (t...@jklm.no) wrote:
+INSTALL_EXEC_HOOKS += \
+ myhostname-install-exec-hook
+
+UNINSTALL_EXEC_HOOKS += \
+ myhostname-uninstall-hook
+endif
Are those hooks necessary? Other libs have hooks only if they are
moved to rootlibdir
2013/1/7 Lennart Poettering lenn...@poettering.net:
Well, for the NSS modules .la files make particularly little sense as
nobody ever links against them except with dlopen() called from inside
libc. And naked dlopen() doesn't know .la files, hence we can just
unconditionally remove them.
On Mon, 07.01.13 19:47, Michael Biebl (mbi...@gmail.com) wrote:
2013/1/7 Lennart Poettering lenn...@poettering.net:
Well, for the NSS modules .la files make particularly little sense as
nobody ever links against them except with dlopen() called from inside
libc. And naked dlopen()
On Mon, Jan 07, 2013 at 03:14:42PM +0100, Lennart Poettering wrote:
On Sun, 06.01.13 10:46, Bryan Kadzban (br...@kadzban.is-a-geek.net) wrote:
On Linux the .la files are probably not necessary for shared libs, no --
but using libtool to find them still is, if the code ever expects to
2013/1/7 Lennart Poettering lenn...@poettering.net:
On Mon, 07.01.13 19:47, Michael Biebl (mbi...@gmail.com) wrote:
Well, there is libltdl which ttbomk requires the .la files for dlopen.
Not that this matters much for systemd, though.
libltdl doesn't need .la files really.
Good to know. It
On Mon, Jan 7, 2013 at 8:29 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Mon, Jan 07, 2013 at 03:14:42PM +0100, Lennart Poettering wrote:
On Sun, 06.01.13 10:46, Bryan Kadzban (br...@kadzban.is-a-geek.net) wrote:
On Linux the .la files are probably not necessary for shared libs,
2013/1/8 Kay Sievers k...@vrfy.org:
Maybe it isn't worth to do it in the buildsys, and we leave it to the
packagers
Sounds like the most sensible approach to me.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Alexander E. Patrakov wrote:
2013/1/7 Bryan Kadzban br...@kadzban.is-a-geek.net:
Untrue. They're perfectly useful for dynamic linking as well:
http://www.sourceware.org/autobook/autobook/autobook_68.html#SEC68
Second paragraph. Also the page several sections after this one, about
]] Tom Gundersen
This was what the old nss-myhostname did. Lennart: any good reason to
exclude the .la or should nss-myhostname be treated the same as the
other libs?
.la files are only useful for static linking. statically linking
nss-myhostname doesn't make any kind of sense.
(I hold
On Sun, Jan 6, 2013 at 9:03 AM, Tollef Fog Heen tfh...@err.no wrote:
]] Tom Gundersen
This was what the old nss-myhostname did. Lennart: any good reason to
exclude the .la or should nss-myhostname be treated the same as the
other libs?
Do the same for the rest of them. We can decide later
Tollef Fog Heen wrote:
]] Tom Gundersen
This was what the old nss-myhostname did. Lennart: any good reason
to exclude the .la or should nss-myhostname be treated the same as
the other libs?
.la files are only useful for static linking.
Untrue. They're perfectly useful for dynamic
---
Makefile.am | 35 +
configure.ac | 20 +++
src/nss-myhostname/Makefile.am | 62 -
src/nss-myhostname/bootstrap.sh | 66 -
src/nss-myhostname/configure.ac | 79 ---
Sorry, I accidentally dropped the ML.
On Sun, Jan 6, 2013 at 2:01 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Sat, Jan 05, 2013 at 10:58:01PM +0100, Tom Gundersen wrote:
On Sat, Jan 5, 2013 at 10:30 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
17 matches
Mail list logo