Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

linux-pango's pango-querymodules

0 views
Skip to first unread message

Mikhail Teterin

unread,
Sep 17, 2005, 8:33:39 PM9/17/05
to
Hi!

For some reason, the post-install target of the linux-pango
port fails for me every time, because the executable
(/compat/linux/usr/bin/pango-querymodules) fails to find libX11.so.6

Adding an explicit invocation of Linux' ldconfig seems to help, though.
Have you seen such a thing before? I'm using the 32-bit Linux emulation
on FreeBSD-6.0/amd64.

Thanks!

-mi

cvs diff: Diffing .
Index: Makefile
===================================================================
RCS file: /home/pcvs/ports/x11-toolkits/linux-pango/Makefile,v
retrieving revision 1.8
diff -U2 -r1.8 Makefile
--- Makefile 18 Aug 2005 22:34:07 -0000 1.8
+++ Makefile 18 Sep 2005 00:31:36 -0000
@@ -30,4 +30,5 @@
post-install:
@${BRANDELF} -t Linux ${PREFIX}/usr/bin/pango-querymodules
+ @${PREFIX}/sbin/ldconfig /usr/X11R6/lib
@${PREFIX}/usr/bin/pango-querymodules > ${PREFIX}/etc/pango/pango.modules

_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulat...@freebsd.org"

Alexander Leidinger

unread,
Sep 18, 2005, 5:30:47 AM9/18/05
to
On Sat, 17 Sep 2005 20:33:13 -0400
Mikhail Teterin <mi+...@aldan.algebra.com> wrote:

> Hi!
>
> For some reason, the post-install target of the linux-pango
> port fails for me every time, because the executable
> (/compat/linux/usr/bin/pango-querymodules) fails to find libX11.so.6
>
> Adding an explicit invocation of Linux' ldconfig seems to help, though.
> Have you seen such a thing before? I'm using the 32-bit Linux emulation
> on FreeBSD-6.0/amd64.

Are you using a non-default linux_base? The default linux_base includes
the X11 directory in the ld.so.conf, so we don't need the ldconfig
part. Trevor failed to add it to his non-default linux_base versions
even after I told him about the problem (I did it at least once, maybe
more than once).

The reason why the linux_base port has to have this in ld.so.conf
instead of adding it when installing the linux-X11 bits is: the file is
owned by linux_base and no port should modify the files of other ports
if we can avoid it. Adding the directory in the linux_base port doesn't
hurt and causes a less complex de-/installation procedure for the
linux-X11 bits.

Bye,
Alexander.

--
If Bill Gates had a dime for every time a Windows box crashed...
...Oh, wait a minute, he already does.

http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7

Boris Samorodov

unread,
Sep 19, 2005, 2:39:04 AM9/19/05
to
On Sun, 18 Sep 2005 11:29:13 +0200 Alexander Leidinger wrote:
> On Sat, 17 Sep 2005 20:33:13 -0400
> Mikhail Teterin <mi+...@aldan.algebra.com> wrote:

> > For some reason, the post-install target of the linux-pango
> > port fails for me every time, because the executable
> > (/compat/linux/usr/bin/pango-querymodules) fails to find libX11.so.6
> >
> > Adding an explicit invocation of Linux' ldconfig seems to help, though.
> > Have you seen such a thing before? I'm using the 32-bit Linux emulation
> > on FreeBSD-6.0/amd64.

> Are you using a non-default linux_base? The default linux_base includes
> the X11 directory in the ld.so.conf, so we don't need the ldconfig
> part. Trevor failed to add it to his non-default linux_base versions
> even after I told him about the problem (I did it at least once, maybe
> more than once).

> The reason why the linux_base port has to have this in ld.so.conf
> instead of adding it when installing the linux-X11 bits is: the file is
> owned by linux_base and no port should modify the files of other ports
> if we can avoid it. Adding the directory in the linux_base port doesn't
> hurt and causes a less complex de-/installation procedure for the
> linux-X11 bits.

BTW as for linux_base-rh-9 we do have a PR
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/85254

which solve the problem. The PR was opened at 23 Aug. Should we
treat it as a maintainer timeout?


WBR
--
Boris B. Samorodov, Research Engineer
InPharmTech Co, http://www.ipt.ru
Telephone & Internet Service Provider

0 new messages