From: Gabbar Singh <gabbar_singh_new@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot compilation errors (libintl) in cygwin.
Date: Wed, 18 Jul 2007 02:08:07 -0700 (PDT) [thread overview]
Message-ID: <457674.31485.qm@web52109.mail.re2.yahoo.com> (raw)
In-Reply-To: <11662767.post@talk.nabble.com>
Hi,
Thanks for the quick reply. But my makefile.in already has that patch. I am using the latest buildroot. In fact I downloaded it on monday, july 16.
I have libintl_gettext installed on my cygwin but still these errors keep on popping up.
Any info will be helpful.
Regards,
Naren
Hebbar <gururajakr@sanyo.co.in> wrote:
This is an error due a small bus in a make file. the patch is already been
set. u can use the latest version to solve it. Also make sure u have gettext
installed
check this link for solution
http://www.nabble.com/-PATCH--Critical-typo-in--Makefile-tf4073315.html
Regards
Gururaja
Gabbar Singh wrote:
>
> Hi,
> I am trying to build a rootfs for arm9 using buildroot.
> I am getting this error repeatedly. I couldnt find any helpful info on
> googling. could anybody please help me out with this.
>
> $ make
> if [ ! -e "/home/buildroot/toolchain_build_arm/bin/sed" ] ; then \
> mkdir -p "/home/buildroot/toolchain_build_arm/bin"; \
> rm -f "/home/buildroot/toolchain_build_arm/bin/sed"; \
> ln -sf "/usr/bin/sed" "/home/buildroot/toolchain_build_arm
> /bin/sed"; \
> fi
>
> Checking build system dependencies:
> CC clean: Ok
> CXX clean: Ok
> CPP clean: Ok
> CFLAGS clean: Ok
> INCLUDES clean: Ok
> CXXFLAGS clean: Ok
> which installed: Ok
> sed works: Ok (/usr/bin/sed)
> GNU make version '3.81': Ok
> C compiler '/usr/bin/gcc'
> C compiler version '3.4.4': Ok
> C++ compiler '/usr/bin/g++'
> C++ compiler version '3.4.4': Ok
> bison installed: Ok
> flex installed: Ok
> gettext installed: Ok
> makeinfo installed: Ok
> Build system dependencies: Ok
>
> set -x && make MAKE="make -j1" -C /home/buildroot/toolchain_build_arm/uCli
> bc-0.9.29 \
> PREFIX=/home/buildroot/toolchain_build_arm/uClibc_dev/ \
> DEVEL_PREFIX=/usr/ \
> RUNTIME_PREFIX=/home/buildroot/toolchain_build_arm/uClibc_
> dev/ \
> HOSTCC="/usr/bin/gcc" \
> pregen install_dev
> + make 'MAKE=make -j1' -C /home/buildroot/toolchain_build_arm/uClibc-0.9.2
> 9 PREFIX=/home/buildroot/toolchain_build_arm/uClibc_dev/ DEVEL_PREFIX=/usr
> / RUNTIME_PREFIX=/home/buildroot/toolchain_build_arm/uClibc_dev/ HOSTCC=/u
> sr/bin/gcc pregen install_dev
> /bin/sh: /home/arm/usr/bin/arm-linux-uclibcgnueabi-gcc: No such file or di
> rectory
> make[1]: /home/arm/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
> make[1]: Entering directory `/home/buildroot/toolchain_build_arm/uClibc-0.
> 9.29'
> make[1]: /home/arm/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
> make[1]: Entering directory `/home/buildroot/toolchain_build_arm/uClibc-0.
> 9.29'
> make[1]: Entering directory `/home/buildroot/toolchain_build_arm/uClibc-0.
> 9.29'
> /bin/sh: /home/arm/usr/bin/arm-linux-uclibcgnueabi-gcc: No such file or di
> rectory
> make[2]: /home/arm/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
> make[2]: /home/arm/usr/bin/arm-linux-uclibcgnueabi-gcc: Command not found
> /usr/bin/gcc -I/usr/include/ncurses -DCURSES_LOC="" -DLOCALE
> conf.
> o zconf.tab.o -o conf
> conf.o:conf.c:(.text+0xb2): undefined reference to `_libintl_gettext'
> conf.o:conf.c:(.text+0xc6): undefined reference to `_libintl_gettext'
> conf.o:conf.c:(.text+0xda): undefined reference to `_libintl_gettext'
> conf.o:conf.c:(.text+0xf2c): undefined reference to `_libintl_gettext'
> conf.o:conf.c:(.text+0x10c5): undefined reference to `_libintl_gettext'
> conf.o:conf.c:(.text+0x116f): more undefined references to
> `_libintl_gettext' fo
> llow
> collect2: ld returned 1 exit status
> make[2]: *** [conf] Error 1
> make[1]: *** [extra/config/conf] Error 2
> make[1]: Leaving directory `/home/buildroot/toolchain_build_arm/uClibc-0.9
> .29'
> make: *** [/home/buildroot/toolchain_build_arm/uClibc-0.9.29/.configured]
> Error 2
>
>
> Thanks and Regards,
> Naren
>
>
> ---------------------------------
> Need Mail bonding?
> Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
--
View this message in context: http://www.nabble.com/Buildroot-compilation-errors-%28libintl%29-in-cygwin.-tf4101102.html#a11662767
Sent from the BuildRoot mailing list archive at Nabble.com.
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
---------------------------------
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070718/bb2a2e04/attachment.htm
next prev parent reply other threads:[~2007-07-18 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 4:51 [Buildroot] Buildroot compilation errors (libintl) in cygwin Gabbar Singh
2007-07-18 5:34 ` Hebbar
2007-07-18 9:08 ` Gabbar Singh [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-18 9:59 Gururaja Hebbar K R
[not found] <6311fe0b0707180831sca30362ve3369fdcbafed7b1@mail.gmail.com>
2007-07-19 3:56 ` Gabbar Singh
2007-07-19 6:46 ` Tom
2007-07-19 13:51 ` Rex Ashbaugh
2007-07-19 17:49 ` Tom
2007-07-20 4:05 ` Gabbar Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=457674.31485.qm@web52109.mail.re2.yahoo.com \
--to=gabbar_singh_new@yahoo.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox