* [Buildroot] Glib2 build problem @ 2008-03-25 13:36 Christian SCHWARZ 2008-03-25 14:08 ` John Voltz 0 siblings, 1 reply; 6+ messages in thread From: Christian SCHWARZ @ 2008-03-25 13:36 UTC (permalink / raw) To: buildroot Dear all, I encounter a build problem with glib2 for an ARM11 target. The error message is the following: ---------------snip--------------------- [...] checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... no checking for bindtextdomain in -lintl... no checking if -liconv is needed to use gettext... checking for ngettext in -lintl... no configure: error: *** You must have either have gettext support in your C library, or use the *** GNU gettext library. (http://www.gnu.org/software/gettext/gettext.html ---------------------snap------------------------------------- It seems as though I should configure ngettext support in libintl, but I don't know how to do so. Is the alternative rebuilding the uclibc, similar to what has been discussed on the mailing list?: http://www.nabble.com/Kindly-help-me-to-build-glib2-on-arm926-platform-td12012803.html Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for ARM Linux has been built (previously) with buildroot. thanks for any hints, Christian ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Glib2 build problem 2008-03-25 13:36 [Buildroot] Glib2 build problem Christian SCHWARZ @ 2008-03-25 14:08 ` John Voltz 2008-03-25 14:19 ` Christian SCHWARZ 0 siblings, 1 reply; 6+ messages in thread From: John Voltz @ 2008-03-25 14:08 UTC (permalink / raw) To: buildroot Take a look inside config.log. You can find the compiler error there that caused the configure script to fail. That usually tells a lot about the real problem. John On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ <christian.schwarz@st.com> wrote: > Dear all, > > I encounter a build problem with glib2 for an ARM11 target. The error > message is the following: > > ---------------snip--------------------- > [...] > checking libintl.h usability... yes > checking libintl.h presence... yes > checking for libintl.h... yes > checking for ngettext in libc... no > checking for bindtextdomain in -lintl... no > checking if -liconv is needed to use gettext... > checking for ngettext in -lintl... no > configure: error: > *** You must have either have gettext support in your C library, or use > the > *** GNU gettext library. (http://www.gnu.org/software/gettext/gettext.html > ---------------------snap------------------------------------- > > It seems as though I should configure ngettext support in libintl, but I > don't know how to do so. Is the alternative rebuilding the uclibc, > similar to what has been discussed on the mailing list?: > > http://www.nabble.com/Kindly-help-me-to-build-glib2-on-arm926-platform-td12012803.html > > Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for ARM > Linux has been built (previously) with buildroot. > > thanks for any hints, > Christian > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/buildroot/attachments/20080325/9b781b9a/attachment.htm ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Glib2 build problem 2008-03-25 14:08 ` John Voltz @ 2008-03-25 14:19 ` Christian SCHWARZ 2008-03-25 14:38 ` John Voltz 0 siblings, 1 reply; 6+ messages in thread From: Christian SCHWARZ @ 2008-03-25 14:19 UTC (permalink / raw) To: buildroot ok thanks, in fact the linker did not find libintl: arm-linux-uclibc/bin/ld: cannot find -lintl Do you have an idea how I can tell the toolchain to look also in $(BUILDROOT)/linux-toolchain/include and $(BUILDROOT)/linux-toolchain/lib ? If not, I have to copy generated libs & header files into the toolchain's own lib/ and include/ dirs. cheers, Christian John Voltz wrote: > Take a look inside config.log. You can find the compiler error there > that caused the configure script to fail. That usually tells a lot about > the real problem. > > John > > > On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ > <christian.schwarz at st.com <mailto:christian.schwarz@st.com>> wrote: > > Dear all, > > I encounter a build problem with glib2 for an ARM11 target. The error > message is the following: > > ---------------snip--------------------- > [...] > checking libintl.h usability... yes > checking libintl.h presence... yes > checking for libintl.h... yes > checking for ngettext in libc... no > checking for bindtextdomain in -lintl... no > checking if -liconv is needed to use gettext... > checking for ngettext in -lintl... no > configure: error: > *** You must have either have gettext support in your C library, or > use the > *** GNU gettext library. > (http://www.gnu.org/software/gettext/gettext.html > ---------------------snap------------------------------------- > > It seems as though I should configure ngettext support in libintl, but I > don't know how to do so. Is the alternative rebuilding the uclibc, > similar to what has been discussed on the mailing list?: > http://www.nabble.com/Kindly-help-me-to-build-glib2-on-arm926-platform-td12012803.html > > Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for ARM > Linux has been built (previously) with buildroot. > > thanks for any hints, > Christian > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org <mailto:buildroot@uclibc.org> > http://busybox.net/mailman/listinfo/buildroot > > > > ------------------------------------------------------------------------ > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Glib2 build problem 2008-03-25 14:19 ` Christian SCHWARZ @ 2008-03-25 14:38 ` John Voltz 2008-03-25 14:42 ` John Voltz 0 siblings, 1 reply; 6+ messages in thread From: John Voltz @ 2008-03-25 14:38 UTC (permalink / raw) To: buildroot I don't have any experience using buildroot with an external toolchain. Maybe someone else here can help with that one. I know a very nasty and hackish way though, you could symlink the include and lib directories out to the external toolchain. If you don't mind polluting your toolchain directories. John On Tue, Mar 25, 2008 at 10:19 AM, Christian SCHWARZ < christian.schwarz@st.com> wrote: > ok thanks, in fact the linker did not find libintl: > arm-linux-uclibc/bin/ld: cannot find -lintl > > Do you have an idea how I can tell the toolchain to look also in > $(BUILDROOT)/linux-toolchain/include and > $(BUILDROOT)/linux-toolchain/lib ? If not, I have to copy generated libs > & header files into the toolchain's own lib/ and include/ dirs. > > cheers, > Christian > > John Voltz wrote: > > Take a look inside config.log. You can find the compiler error there > > that caused the configure script to fail. That usually tells a lot about > > the real problem. > > > > John > > > > > > On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ > > <christian.schwarz at st.com <mailto:christian.schwarz@st.com>> wrote: > > > > Dear all, > > > > I encounter a build problem with glib2 for an ARM11 target. The > error > > message is the following: > > > > ---------------snip--------------------- > > [...] > > checking libintl.h usability... yes > > checking libintl.h presence... yes > > checking for libintl.h... yes > > checking for ngettext in libc... no > > checking for bindtextdomain in -lintl... no > > checking if -liconv is needed to use gettext... > > checking for ngettext in -lintl... no > > configure: error: > > *** You must have either have gettext support in your C library, or > > use the > > *** GNU gettext library. > > (http://www.gnu.org/software/gettext/gettext.html > > ---------------------snap------------------------------------- > > > > It seems as though I should configure ngettext support in libintl, > but I > > don't know how to do so. Is the alternative rebuilding the uclibc, > > similar to what has been discussed on the mailing list?: > > > http://www.nabble.com/Kindly-help-me-to-build-glib2-on-arm926-platform-td12012803.html > > > > Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for > ARM > > Linux has been built (previously) with buildroot. > > > > thanks for any hints, > > Christian > > > > _______________________________________________ > > buildroot mailing list > > buildroot at uclibc.org <mailto:buildroot@uclibc.org> > > http://busybox.net/mailman/listinfo/buildroot > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > buildroot mailing list > > buildroot at uclibc.org > > http://busybox.net/mailman/listinfo/buildroot > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/buildroot/attachments/20080325/63d4cbf6/attachment.htm ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Glib2 build problem 2008-03-25 14:38 ` John Voltz @ 2008-03-25 14:42 ` John Voltz 2008-03-25 14:51 ` Christian SCHWARZ 0 siblings, 1 reply; 6+ messages in thread From: John Voltz @ 2008-03-25 14:42 UTC (permalink / raw) To: buildroot ln -s $(BUILDROOT)/linux-toolchain/lib $(BUILDROOT)/$(STAGING_DIR)/lib ln -s $(BUILDROOT)/$(STAGING_DIR)/lib $(BUILDROOT)/$(STAGING_DIR)/usr/lib ln -s $(BUILDROOT)/linux-toolchain/include $(BUILDROOT)/$(STAGING_DIR)/usr/include Note that gcc 4.2 and later support sysroot so staging_dir/usr is actually a directory and not a symlink to dot. John On Tue, Mar 25, 2008 at 10:38 AM, John Voltz <john.voltz@gmail.com> wrote: > I don't have any experience using buildroot with an external toolchain. > Maybe someone else here can help with that one. I know a very nasty and > hackish way though, you could symlink the include and lib directories out to > the external toolchain. If you don't mind polluting your toolchain > directories. > > John > > > On Tue, Mar 25, 2008 at 10:19 AM, Christian SCHWARZ < > christian.schwarz at st.com> wrote: > > > ok thanks, in fact the linker did not find libintl: > > arm-linux-uclibc/bin/ld: cannot find -lintl > > > > Do you have an idea how I can tell the toolchain to look also in > > $(BUILDROOT)/linux-toolchain/include and > > $(BUILDROOT)/linux-toolchain/lib ? If not, I have to copy generated libs > > & header files into the toolchain's own lib/ and include/ dirs. > > > > cheers, > > Christian > > > > John Voltz wrote: > > > Take a look inside config.log. You can find the compiler error there > > > that caused the configure script to fail. That usually tells a lot > > about > > > the real problem. > > > > > > John > > > > > > > > > On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ > > > <christian.schwarz at st.com <mailto:christian.schwarz@st.com>> wrote: > > > > > > Dear all, > > > > > > I encounter a build problem with glib2 for an ARM11 target. The > > error > > > message is the following: > > > > > > ---------------snip--------------------- > > > [...] > > > checking libintl.h usability... yes > > > checking libintl.h presence... yes > > > checking for libintl.h... yes > > > checking for ngettext in libc... no > > > checking for bindtextdomain in -lintl... no > > > checking if -liconv is needed to use gettext... > > > checking for ngettext in -lintl... no > > > configure: error: > > > *** You must have either have gettext support in your C library, > > or > > > use the > > > *** GNU gettext library. > > > (http://www.gnu.org/software/gettext/gettext.html > > > ---------------------snap------------------------------------- > > > > > > It seems as though I should configure ngettext support in libintl, > > but I > > > don't know how to do so. Is the alternative rebuilding the uclibc, > > > similar to what has been discussed on the mailing list?: > > > > > http://www.nabble.com/Kindly-help-me-to-build-glib2-on-arm926-platform-td12012803.html > > > > > > Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for > > ARM > > > Linux has been built (previously) with buildroot. > > > > > > thanks for any hints, > > > Christian > > > > > > _______________________________________________ > > > buildroot mailing list > > > buildroot at uclibc.org <mailto:buildroot@uclibc.org> > > > http://busybox.net/mailman/listinfo/buildroot > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > buildroot mailing list > > > buildroot at uclibc.org > > > http://busybox.net/mailman/listinfo/buildroot > > _______________________________________________ > > buildroot mailing list > > buildroot at uclibc.org > > http://busybox.net/mailman/listinfo/buildroot > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/buildroot/attachments/20080325/b4ccd1ef/attachment-0001.htm ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Glib2 build problem 2008-03-25 14:42 ` John Voltz @ 2008-03-25 14:51 ` Christian SCHWARZ 0 siblings, 0 replies; 6+ messages in thread From: Christian SCHWARZ @ 2008-03-25 14:51 UTC (permalink / raw) To: buildroot Yes, this is what I now do, however, as you already mentioned it is not a very clean way (but maybe the only one?). //Christian John Voltz wrote: > ln -s $(BUILDROOT)/linux-toolchain/lib $(BUILDROOT)/$(STAGING_DIR)/lib > ln -s $(BUILDROOT)/$(STAGING_DIR)/lib $(BUILDROOT)/$(STAGING_DIR)/usr/lib > ln -s $(BUILDROOT)/linux-toolchain/include > $(BUILDROOT)/$(STAGING_DIR)/usr/include > > Note that gcc 4.2 and later support sysroot so staging_dir/usr is > actually a directory and not a symlink to dot. > > John > > On Tue, Mar 25, 2008 at 10:38 AM, John Voltz <john.voltz@gmail.com > <mailto:john.voltz@gmail.com>> wrote: > > I don't have any experience using buildroot with an external > toolchain. Maybe someone else here can help with that one. I know a > very nasty and hackish way though, you could symlink the include and > lib directories out to the external toolchain. If you don't mind > polluting your toolchain directories. > > John > > > On Tue, Mar 25, 2008 at 10:19 AM, Christian SCHWARZ > <christian.schwarz at st.com <mailto:christian.schwarz@st.com>> wrote: > > ok thanks, in fact the linker did not find libintl: > arm-linux-uclibc/bin/ld: cannot find -lintl > > Do you have an idea how I can tell the toolchain to look also in > $(BUILDROOT)/linux-toolchain/include and > $(BUILDROOT)/linux-toolchain/lib ? If not, I have to copy > generated libs > & header files into the toolchain's own lib/ and include/ dirs. > > cheers, > Christian > > John Voltz wrote: > > Take a look inside config.log. You can find the compiler > error there > > that caused the configure script to fail. That usually tells > a lot about > > the real problem. > > > > John > > > > > > On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ > > <christian.schwarz at st.com <mailto:christian.schwarz@st.com> > <mailto:christian.schwarz@st.com > <mailto:christian.schwarz@st.com>>> wrote: > > > > Dear all, > > > > I encounter a build problem with glib2 for an ARM11 > target. The error > > message is the following: > > > > ---------------snip--------------------- > > [...] > > checking libintl.h usability... yes > > checking libintl.h presence... yes > > checking for libintl.h... yes > > checking for ngettext in libc... no > > checking for bindtextdomain in -lintl... no > > checking if -liconv is needed to use gettext... > > checking for ngettext in -lintl... no > > configure: error: > > *** You must have either have gettext support in your C > library, or > > use the > > *** GNU gettext library. > > (http://www.gnu.org/software/gettext/gettext.html > > > ---------------------snap------------------------------------- > > > > It seems as though I should configure ngettext support in > libintl, but I > > don't know how to do so. Is the alternative rebuilding > the uclibc, > > similar to what has been discussed on the mailing list?: > > > http://www.nabble.com/Kindly-help-me-to-build-glib2-on-arm926-platform-td12012803.html > > > > Buildroot snapshot is 2008-17-03. A cross-compiling > toolchain for ARM > > Linux has been built (previously) with buildroot. > > > > thanks for any hints, > > Christian > > > > _______________________________________________ > > buildroot mailing list > > buildroot at uclibc.org <mailto:buildroot@uclibc.org> > <mailto:buildroot at uclibc.org <mailto:buildroot@uclibc.org>> > > http://busybox.net/mailman/listinfo/buildroot > > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > buildroot mailing list > > buildroot at uclibc.org <mailto:buildroot@uclibc.org> > > http://busybox.net/mailman/listinfo/buildroot > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org <mailto:buildroot@uclibc.org> > http://busybox.net/mailman/listinfo/buildroot > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-03-25 14:51 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2008-03-25 13:36 [Buildroot] Glib2 build problem Christian SCHWARZ 2008-03-25 14:08 ` John Voltz 2008-03-25 14:19 ` Christian SCHWARZ 2008-03-25 14:38 ` John Voltz 2008-03-25 14:42 ` John Voltz 2008-03-25 14:51 ` Christian SCHWARZ
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox