Re: Am I Missing A Compat Library?
On Mon, 18 Jul 2011 10:11:28 -0500, Tim Daneliuk wrote: I just ran pkg_libchk and got this: avahi-app-0.6.29: /usr/local/lib/libavahi-glib.so.1 misses libicui18n.so.46 As I've never seen this before, I'm unclear on what to do to remmediate. Seems to originate from Unicode support. The devel/icu port should be the one to bring this library. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Am I Missing A Compat Library?
On Mon, Jul 18, 2011 at 10:11:28AM -0500, Tim Daneliuk wrote: I just ran pkg_libchk and got this: avahi-app-0.6.29: /usr/local/lib/libavahi-glib.so.1 misses libicui18n.so.46 As I've never seen this before, I'm unclear on what to do to remmediate. Have you updated your ports recently? The ICU port was updated to version 4.8 recently, which provides libicui18n.so.48, and replaced libicui18n.so.46. As noted in /usr/ports/UPDATING, all ports that depend on ICU should be updated. For some unknown reason this dependency was not resolved when you updated your ports. Recompile the avahi-app port and it should link with the newer version and work fine again. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp95Znb5UTxk.pgp Description: PGP signature
Re: Am I Missing A Compat Library?
On 7/18/2011 11:23 AM, Roland Smith said this:
On Mon, Jul 18, 2011 at 10:11:28AM -0500, Tim Daneliuk wrote:
I just ran pkg_libchk and got this:
avahi-app-0.6.29: /usr/local/lib/libavahi-glib.so.1 misses libicui18n.so.46
As I've never seen this before, I'm unclear on what to do to remmediate.
Have you updated your ports recently? The ICU port was updated to version 4.8
Yes.
recently, which provides libicui18n.so.48, and replaced libicui18n.so.46. As
noted in /usr/ports/UPDATING, all ports that depend on ICU should be updated.
I did this (and what a joy THAT was ;)
For some unknown reason this dependency was not resolved when you updated your
ports.
Apparently.
Recompile the avahi-app port and it should link with the newer version and
work fine again.
The compilation is blowing out (that might explain the observed problem).
That is, the port does not build properly - apparently there is some
syntax problem in the code:
/usr/include/machine/endian.h:107: syntax error, unexpected '{' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at '{'
/usr/include/machine/endian.h:107: syntax error, unexpected ';' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libicui18n.so.46 not found, required by
libavahi-glib.so.1
Command
'['/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectop_Yoq/Avahi-0.6',
'--introspect-dump=/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectop_Yoq/types.txt,/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectop_Yoq/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr1/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr1/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Roland
--
Tim Daneliuk
tun...@tundraware.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Am I Missing A Compat Library?
On Mon, Jul 18, 2011 at 11:35:33AM -0500, Tim Daneliuk wrote:
On 7/18/2011 11:23 AM, Roland Smith said this:
On Mon, Jul 18, 2011 at 10:11:28AM -0500, Tim Daneliuk wrote:
I just ran pkg_libchk and got this:
avahi-app-0.6.29: /usr/local/lib/libavahi-glib.so.1 misses
libicui18n.so.46
As I've never seen this before, I'm unclear on what to do to remmediate.
Have you updated your ports recently? The ICU port was updated to version
4.8
Yes.
recently, which provides libicui18n.so.48, and replaced libicui18n.so.46. As
noted in /usr/ports/UPDATING, all ports that depend on ICU should be
updated.
I did this (and what a joy THAT was ;)
Indeed. :-/ Almost but not quite as much fun as a gettext update.
Recompile the avahi-app port and it should link with the newer version and
work fine again.
The compilation is blowing out (that might explain the observed problem).
That is, the port does not build properly - apparently there is some
syntax problem in the code:
/usr/include/machine/endian.h:107: syntax error, unexpected '{' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at '{'
/usr/include/machine/endian.h:107: syntax error, unexpected ';' in ' return
(__extension__ ({ register __uint32_t __X = (_x); __asm (bswap %0 : +r
(__X)); __X; }));' at ';'
I get the same messages from as well. They do not cause the error.
/libexec/ld-elf.so.1: Shared object libicui18n.so.46 not found, required by
libavahi-glib.so.1
But I _don't_ get this linker error. Just a thought, but have a look at glib
and dbus, and check that it is linked to the right libicu? ('ldd
/usr/local/lib/libglib-2.0.so.0' and 'ldd /usr/local/lib/libdbus-glib-1.so.2')
If that is not the case, you'll have to dive into the configure output, I
think.
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgprRdadP1gFh.pgp
Description: PGP signature
Re: Am I Missing A Compat Library?
On 7/18/2011 12:43 PM, Roland Smith said this:
But I _don't_ get this linker error. Just a thought, but have a look at glib
and dbus, and check that it is linked to the right libicu? ('ldd
/usr/local/lib/libglib-2.0.so.0' and 'ldd /usr/local/lib/libdbus-glib-1.so.2')
If that is not the case, you'll have to dive into the configure output, I
think.
Roland
A forced deinstallation of avahi-app and then an installation, seems
to have made the problem disappear.
So much for dynamically liked libraries will make systems maintenance
simpler ...
Tim Daneliuk
tun...@tundraware.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Am I Missing A Compat Library?
In the last episode (Jul 18), Tim Daneliuk said:
On 7/18/2011 12:43 PM, Roland Smith said this:
But I _don't_ get this linker error. Just a thought, but have a look at
glib and dbus, and check that it is linked to the right libicu? ('ldd
/usr/local/lib/libglib-2.0.so.0' and 'ldd
/usr/local/lib/libdbus-glib-1.so.2')
If that is not the case, you'll have to dive into the configure output,
I think.
A forced deinstallation of avahi-app and then an installation, seems to
have made the problem disappear.
So much for dynamically liked libraries will make systems maintenance
simpler ...
BTW, Both portupgrade and portmaster (with the -w flag) will copy old shared
libraries to /usr/local/lib/compat/pkg/ during an upgrade, so that programs
linked to them will still run.
--
Dan Nelson
dnel...@allantgroup.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Am I Missing A Compat Library?
On Mon, Jul 18, 2011 at 01:02:53PM -0500, Tim Daneliuk wrote:
On 7/18/2011 12:43 PM, Roland Smith said this:
But I _don't_ get this linker error. Just a thought, but have a look at glib
and dbus, and check that it is linked to the right libicu? ('ldd
/usr/local/lib/libglib-2.0.so.0' and 'ldd
/usr/local/lib/libdbus-glib-1.so.2')
If that is not the case, you'll have to dive into the configure output, I
think.
Roland
A forced deinstallation of avahi-app and then an installation, seems
to have made the problem disappear.
I've seen that problem before. Sometimes an app will link to the previously
installed versions of its libraries rather than the freshly built ones. Do you
by any chance have the environment variable LIBRARY_PATH set to
/usr/local/lib? I've long suspected that or the -L option to gcc to be the
culprit.
So much for dynamically linked libraries will make systems maintenance
simpler ...
Static linking does indeed have some advantages. :-) Of course there is still
the option WITHOUT_DYNAMICROOT in /etc/src.conf to build /bin and /sbin
without dynamic linking... Haven't tried it in years, though.
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpSpgchaI8Sx.pgp
Description: PGP signature
Re: Am I Missing A Compat Library?
On 7/18/2011 3:15 PM, Roland Smith said this:
On Mon, Jul 18, 2011 at 01:02:53PM -0500, Tim Daneliuk wrote:
On 7/18/2011 12:43 PM, Roland Smith said this:
But I _don't_ get this linker error. Just a thought, but have a look at glib
and dbus, and check that it is linked to the right libicu? ('ldd
/usr/local/lib/libglib-2.0.so.0' and 'ldd
/usr/local/lib/libdbus-glib-1.so.2')
If that is not the case, you'll have to dive into the configure output, I
think.
Roland
A forced deinstallation of avahi-app and then an installation, seems
to have made the problem disappear.
I've seen that problem before. Sometimes an app will link to the previously
installed versions of its libraries rather than the freshly built ones. Do you
by any chance have the environment variable LIBRARY_PATH set to
/usr/local/lib? I've long suspected that or the -L option to gcc to be the
culprit.
Nope.
So much for dynamically linked libraries will make systems maintenance
simpler ...
Static linking does indeed have some advantages. :-) Of course there is still
the option WITHOUT_DYNAMICROOT in /etc/src.conf to build /bin and /sbin
without dynamic linking... Haven't tried it in years, though.
Disk space is cheap. Time wasted fixing silly problems is irreplacable.
--
Tim Daneliuk
tun...@tundraware.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
