Re: libiconv pulled in by pkg upgrade? lots of errors after that
On Sun, 23 Feb 2014 20:05:36 -0800 (PST) Thomas Mueller wrote: > from Tijl Coosemans: >> On Sun, 23 Feb 2014 10:57:12 + (UTC) Thomas Mueller wrote: >>> Now I want to know what would happen if I rebuild system with >>> WITHOUT_ICONV=yes >>> in /etc/src.conf >>> and use libiconv from ports. >>> >>> Would it work, and would I have to rebuild all ports? >> >> It would work and it's probably easiest to rebuild all ports. Technically >> you only need to rebuild these packages: >> >> grep -Rl __bsd_iconv /usr/local | xargs -n1 pkg which | sed 's/.* //' | sort >> -u >> >>> It seems including libiconv in base has adverse side effects, the two >>> can clash when both base and ports libiconv are installed. >> >> The two can coexist. It's just that some care must be taken during >> compilation. > > I guess I need to check which ports use which shared libraries, using > pkg? > > So maybe I don't need WITHOUT_ICONV in /etc/src.conf ? > > Maybe base iconv could be enhanced to be identical to the port, by > adding wchar_t support? > > I like Lev Serebryakov's idea of a notice in UPDATING, and would add > that such a notice on possible iconv conflicts could be added tp > UPDATING for both the ports tree and system-source tree. When I said that some care must be taken during compilation, I meant by port maintainers, not by users, so indeed you don't need WITHOUT_ICONV. In fact there's nothing special you need to do at all that would require an entry in UPDATING. If a port depends on libiconv then just let them like with any other dependency. If a port doesn't build with libiconv installed then just report that like with any other build failure. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
from Tijl Coosemans: > On Sun, 23 Feb 2014 10:57:12 + (UTC) Thomas Mueller wrote: > > From other posts on emailing lists, I see libiconv from ports supports > > utf-8, while base (>=10) does not. > No, utf-8 works fine with base iconv. Base iconv does not recognise the > special encoding named "wchar_t" which means whatever encoding is used for > the C/C++ type wchar_t with libiconv. > > Now I want to know what would happen if I rebuild system with > > WITHOUT_ICONV=yes > > in /etc/src.conf > > and use libiconv from ports. > > > Would it work, and would I have to rebuild all ports? > It would work and it's probably easiest to rebuild all ports. Technically > you only need to rebuild these packages: > grep -Rl __bsd_iconv /usr/local | xargs -n1 pkg which | sed 's/.* //' | sort > -u > > It seems including libiconv in base has adverse side effects, the two > > can clash when both base and ports libiconv are installed. > The two can coexist. It's just that some care must be taken during > compilation. I guess I need to check which ports use which shared libraries, using pkg? So maybe I don't need WITHOUT_ICONV in /etc/src.conf ? Maybe base iconv could be enhanced to be identical to the port, by adding wchar_t support? I like Lev Serebryakov's idea of a notice in UPDATING, and would add that such a notice on possible iconv conflicts could be added tp UPDATING for both the ports tree and system-source tree. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
On Sun, 23 Feb 2014 10:57:12 + (UTC) Thomas Mueller wrote: > From other posts on emailing lists, I see libiconv from ports supports > utf-8, while base (>=10) does not. No, utf-8 works fine with base iconv. Base iconv does not recognise the special encoding named "wchar_t" which means whatever encoding is used for the C/C++ type wchar_t with libiconv. > Now I want to know what would happen if I rebuild system with > WITHOUT_ICONV=yes > in /etc/src.conf > and use libiconv from ports. > > Would it work, and would I have to rebuild all ports? It would work and it's probably easiest to rebuild all ports. Technically you only need to rebuild these packages: grep -Rl __bsd_iconv /usr/local | xargs -n1 pkg which | sed 's/.* //' | sort -u > It seems including libiconv in base has adverse side effects, the two > can clash when both base and ports libiconv are installed. The two can coexist. It's just that some care must be taken during compilation. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
On Sun, 23 Feb 2014 03:43:58 -0800 (PST) Anton Shterenlikht wrote: > From t...@freebsd.org Sun Feb 23 11:21:17 2014 >> On Sun, 23 Feb 2014 00:51:34 -0800 (PST) Anton Shterenlikht wrote: >>> pkg upgrade pulled libiconv. >>> Now I get errors like: >>> >>> # gphoto2 -l >>> /usr/local/lib/libgphoto2/2.5.3.1/ptp2.so: Undefined symbol >>> "__bsd_iconv_open" >>> >>> firefox >>> /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" >> >> This symbol is in libc: >> >> % readelf -s /lib/libc.so.7 | grep __bsd_iconv_open >> 759: 0004598041 FUNCGLOBAL DEFAULT 11 __bsd_iconv_open@@FBSD_1.3 >> 2558: 00045aa050 FUNCGLOBAL DEFAULT 11 >> __bsd_iconv_open_into@@FBSD_1.3 >> >> If that's not the case on your system you need to update world. > > # readelf -s /lib/libc.so.7 | grep __bsd_iconv_open > # > > Thanks, will do. > Perhaps this issue should be addressed in UPDATING.. > I'm at r257910. You need at least r258587. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
>From t...@freebsd.org Sun Feb 23 11:21:17 2014 > >On Sun, 23 Feb 2014 00:51:34 -0800 (PST) Anton Shterenlikht wrote: >> pkg upgrade pulled libiconv. >> Now I get errors like: >> >> # gphoto2 -l >> /usr/local/lib/libgphoto2/2.5.3.1/ptp2.so: Undefined symbol >> "__bsd_iconv_open" >> >> firefox >> /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" > >This symbol is in libc: > >% readelf -s /lib/libc.so.7 | grep __bsd_iconv_open > 759: 0004598041 FUNCGLOBAL DEFAULT 11 __bsd_iconv_open@@FBSD_1.3 > 2558: 00045aa050 FUNCGLOBAL DEFAULT 11 > __bsd_iconv_open_into@@FBSD_1.3 > >If that's not the case on your system you need to update world. > # readelf -s /lib/libc.so.7 | grep __bsd_iconv_open # Thanks, will do. Perhaps this issue should be addressed in UPDATING.. I'm at r257910. Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
>From swhet...@gmail.com Sun Feb 23 11:21:05 2014 > >On Sun, Feb 23, 2014 at 2:51 AM, Anton Shterenlikht wrote: >> pkg upgrade pulled libiconv. >> Now I get errors like: >> >> # gphoto2 -l >> /usr/local/lib/libgphoto2/2.5.3.1/ptp2.so: Undefined symbol >> "__bsd_iconv_open" >> >> firefox >> /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" >> >> If I delete libiconv, then I get: >> >> firefox >> XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so: >> Shared object "libiconv.so.3" not found, required by "libdbus-glib-1.so.2" >> Couldn't load XPCOM. >> >> so I probably now need to rebuild all these ports >> manually: >> >> [1/1] Deleting libiconv-1.14_1... >> libiconv-1.14_1 is required by: glib-2.36.3_2 gobject-introspection-1.36.0_2 >> libIDL-0.8.14_1 polkit-0.105_1 cairo-1.10.2_7,2 pango-1.34.1_1 >> consolekit-0.4.3 librsvg2-2.36.4 gconf2-2.32.0_3, deleting anyway >> >> Anyway, I thought libiconv was gone for good >> from ports, as it is available in base from 10. >> I'm on 11-current, so not sure what's going on. >> >There are some ports (i.e php-iconvm devel/glib2) that require the >libiconv port due to they rely on a gnu feature that is not >implemented in FreeBSD'x posix compliant libiconv in base. > >The message in devel/glib2/Makefile: > ># iconv:wchar_t - our iconv in base doesn't support utf-8 -> wchar_t (b) ># (wchar_t is used by glibmm, rawtherapee triggered this) >USES= gettext gmake iconv:wchar_t pathfix pkgconfig shebangfix perl5 ok, but I'm still not clear how to recover from this. pkg check -srda doesn't report any issues, yet: $ firefox /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" $ monsterz Traceback (most recent call last): File "/usr/local/share/monsterz/monsterz.py", line 15, in import pygame File "/usr/local/lib/python2.7/site-packages/pygame/__init__.py", line 95, in from pygame.base import * ImportError: /usr/local/lib/libSDL-1.2.so.11: Undefined symbol "__bsd_iconv" So what's going on? Thanks Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
On Sun, 23 Feb 2014 00:51:34 -0800 (PST) Anton Shterenlikht wrote: > pkg upgrade pulled libiconv. > Now I get errors like: > > # gphoto2 -l > /usr/local/lib/libgphoto2/2.5.3.1/ptp2.so: Undefined symbol > "__bsd_iconv_open" > > firefox > /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" This symbol is in libc: % readelf -s /lib/libc.so.7 | grep __bsd_iconv_open 759: 0004598041 FUNCGLOBAL DEFAULT 11 __bsd_iconv_open@@FBSD_1.3 2558: 00045aa050 FUNCGLOBAL DEFAULT 11 __bsd_iconv_open_into@@FBSD_1.3 If that's not the case on your system you need to update world. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
> pkg upgrade pulled libiconv. > Now I get errors like: > # gphoto2 -l > /usr/local/lib/libgphoto2/2.5.3.1/ptp2.so: Undefined symbol "__bsd_iconv_open" > firefox > /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" > If I delete libiconv, then I get: > firefox > XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so: > Shared object "libiconv.so.3" not found, required by "libdbus-glib-1.so.2" > Couldn't load XPCOM. > so I probably now need to rebuild all these ports > manually: > [1/1] Deleting libiconv-1.14_1... > libiconv-1.14_1 is required by: glib-2.36.3_2 gobject-introspection-1.36.0_2 > libIDL-0.8.14_1 polkit-0.105_1 cairo-1.10.2_7,2 pango-1.34.1_1 > consolekit-0.4.3 > librsvg2-2.36.4 gconf2-2.32.0_3, deleting anyway > Anyway, I thought libiconv was gone for good > from ports, as it is available in base from 10. > I'm on 11-current, so not sure what's going on. > Thanks > Anton >From other posts on emailing lists, I see libiconv from ports supports utf-8, >while base (>=10) does not. Now I want to know what would happen if I rebuild system with WITHOUT_ICONV=yes in /etc/src.conf and use libiconv from ports. Would it work, and would I have to rebuild all ports? Fortunately, I am not yet very advanced in building ports for FreeBSD 10-STABLE and 11-current. It seems including libiconv in base has adverse side effects, the two can clash when both base and ports libiconv are installed. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libiconv pulled in by pkg upgrade? lots of errors after that
On Sun, Feb 23, 2014 at 2:51 AM, Anton Shterenlikht wrote: > pkg upgrade pulled libiconv. > Now I get errors like: > > # gphoto2 -l > /usr/local/lib/libgphoto2/2.5.3.1/ptp2.so: Undefined symbol "__bsd_iconv_open" > > firefox > /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" > > If I delete libiconv, then I get: > > firefox > XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so: > Shared object "libiconv.so.3" not found, required by "libdbus-glib-1.so.2" > Couldn't load XPCOM. > > so I probably now need to rebuild all these ports > manually: > > [1/1] Deleting libiconv-1.14_1... > libiconv-1.14_1 is required by: glib-2.36.3_2 gobject-introspection-1.36.0_2 > libIDL-0.8.14_1 polkit-0.105_1 cairo-1.10.2_7,2 pango-1.34.1_1 > consolekit-0.4.3 librsvg2-2.36.4 gconf2-2.32.0_3, deleting anyway > > Anyway, I thought libiconv was gone for good > from ports, as it is available in base from 10. > I'm on 11-current, so not sure what's going on. > There are some ports (i.e php-iconvm devel/glib2) that require the libiconv port due to they rely on a gnu feature that is not implemented in FreeBSD'x posix compliant libiconv in base. The message in devel/glib2/Makefile: # iconv:wchar_t - our iconv in base doesn't support utf-8 -> wchar_t (b) # (wchar_t is used by glibmm, rawtherapee triggered this) USES= gettext gmake iconv:wchar_t pathfix pkgconfig shebangfix perl5 -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
libiconv pulled in by pkg upgrade? lots of errors after that
pkg upgrade pulled libiconv. Now I get errors like: # gphoto2 -l /usr/local/lib/libgphoto2/2.5.3.1/ptp2.so: Undefined symbol "__bsd_iconv_open" firefox /usr/local/lib/firefox/libxul.so: Undefined symbol "__bsd_iconv_open" If I delete libiconv, then I get: firefox XPCOMGlueLoad error for file /usr/local/lib/firefox/libxul.so: Shared object "libiconv.so.3" not found, required by "libdbus-glib-1.so.2" Couldn't load XPCOM. so I probably now need to rebuild all these ports manually: [1/1] Deleting libiconv-1.14_1... libiconv-1.14_1 is required by: glib-2.36.3_2 gobject-introspection-1.36.0_2 libIDL-0.8.14_1 polkit-0.105_1 cairo-1.10.2_7,2 pango-1.34.1_1 consolekit-0.4.3 librsvg2-2.36.4 gconf2-2.32.0_3, deleting anyway Anyway, I thought libiconv was gone for good from ports, as it is available in base from 10. I'm on 11-current, so not sure what's going on. Thanks Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
