This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I was looking to enable full locale support in the crosstool toolchain build. The idea was that these could be copied from the toolchain onto the target image to support locales.
First, to do this I changed the configure of glibc to have
'enable-add-ons' which should enable the locales (I think 0.27 has it
this way already, see crosstool.sh). Also I added make localedata/install-locales install_root=${PREFIX}/${TARGET} to the install section.
Sounds good. I'll add that in, but comment it out with a note encouraging people who want locale data to enable it. Or does the locale data not take long to build?
While doing this I noticed that glibc was configured with '--enable-clocale=gnu', with a comment
# The --enable-clocale=gnu is recommended by LFS; see http://bugs.linuxfromscratch.org/show_bug.cgi?id=411
I took a look at this, but it seems that that option should be going to the configure of gcc, not glibc ??
My questions are: ------------------
- Has anyone built full locales with crosstool and installed them onto a target. Is what I'm trying to do valid ?
- Should the '--enable-clocale=gnu' be moved from the configure section of glibc, to the configure section of gcc ?
-- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |