Glib2 build problem

Buildroot Christian SCHWARZ 2 participants 6 messages Mar 25, 2008

lore

Share & tools

lore

Christian SCHWARZ

author

2008-03-25 13:36 UTC #0 lore raw

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

John Voltz

2008-03-25 14:08 UTC #1 lore raw

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

Quoted 29 lines · Christian SCHWARZ

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.

Quoted 8 lines

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

Christian SCHWARZ

author

2008-03-25 14:19 UTC #2 lore raw

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

Quoted 55 lines · John Voltz

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:[email protected]>> 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:[email protected]>
http://busybox.net/mailman/listinfo/buildroot
------------------------------------------------------------------------
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot

John Voltz

2008-03-25 14:38 UTC #3 lore raw

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

Quoted 67 lines · Christian SCHWARZ

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
Quoted 7 lines · John Voltz
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
Quoted 6 lines
On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ <christian.schwarz at st.com <mailto:[email protected]>> wrote:
Dear all,
I encounter a build problem with glib2 for an ARM11 target. The
error
Quoted 18 lines
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-------------------------------------
Quoted 1 line
It seems as though I should configure ngettext support in libintl,
but I
Quoted 3 lines
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
Quoted 2 lines
Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for
ARM
Quoted 14 lines
Linux has been built (previously) with buildroot.
thanks for any hints,
Christian
_______________________________________________
buildroot mailing list
buildroot at uclibc.org <mailto:[email protected]>
http://busybox.net/mailman/listinfo/buildroot
------------------------------------------------------------------------

Quoted 9 lines

Quoted 4 lines
_______________________________________________
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

John Voltz

2008-03-25 14:42 UTC #4 lore raw

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

Quoted 6 lines · John Voltz

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.

Quoted 87 lines

John
Quoted 79 lines · Christian SCHWARZ
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
Quoted 2 lines · John Voltz
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
Quoted 11 lines
the real problem.
John
On Tue, Mar 25, 2008 at 9:36 AM, Christian SCHWARZ <christian.schwarz at st.com <mailto:[email protected]>> wrote:
Dear all,
I encounter a build problem with glib2 for an ARM11 target. The
error
Quoted 13 lines
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
Quoted 6 lines
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
Quoted 3 lines
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
Quoted 2 lines
Buildroot snapshot is 2008-17-03. A cross-compiling toolchain for
ARM
Quoted 13 lines
Linux has been built (previously) with buildroot.
thanks for any hints,
Christian
_______________________________________________
buildroot mailing list
buildroot at uclibc.org <mailto:[email protected]>
http://busybox.net/mailman/listinfo/buildroot
------------------------------------------------------------------------
Quoted 5 lines
_______________________________________________
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

Christian SCHWARZ

author

2008-03-25 14:51 UTC #5 lore raw

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

Quoted 120 lines · John Voltz

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 <[email protected] <mailto:[email protected]>> 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:[email protected]>> 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:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>> 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:[email protected]>
<mailto:buildroot at uclibc.org <mailto:[email protected]>>
> http://busybox.net/mailman/listinfo/buildroot
>
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org <mailto:[email protected]> > http://busybox.net/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot at uclibc.org <mailto:[email protected]>
http://busybox.net/mailman/listinfo/buildroot
------------------------------------------------------------------------
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot