From: Sri Ram Vemulpali <sri.ram.gmu06@gmail.com>
To: linux-kernel-mail <linux-kernel@vger.kernel.org>,
linux-newbie@vger.kernel.org
Cc: dhylands@gmail.com
Subject: Buildroot compilation error
Date: Sun, 19 Feb 2012 11:38:32 -0500 [thread overview]
Message-ID: <CALyraeMK=bEVkBtbi8xAm5aWrCbjGMTkArHygG78tJ86TzzNOw@mail.gmail.com> (raw)
Hello All,
I am using BuildRoot to compile my embedded linux and tool-chain.
After compiling most of the packages and tool-chain I am getting
following error. This occurs when compiling libnl-3.0
make[3]: Entering directory
`/home/sriram/buildroot/buildroot-2011.11/output/build/libnl-3.0/lib'
CC route/pktloc.lo
route/pktloc.c: In function ‘read_pktlocs’:
route/pktloc.c:127:34: error: ‘YY_BUF_SIZE’ undeclared (first use in
this function)
route/pktloc.c:127:34: note: each undeclared identifier is reported
only once for each function it appears in
make[3]: *** [route/pktloc.lo] Error 1
make[3]: Leaving directory
`/home/sriram/buildroot/buildroot-2011.11/output/build/libnl-3.0/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/sriram/buildroot/buildroot-2011.11/output/build/libnl-3.0/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/sriram/buildroot/buildroot-2011.11/output/build/libnl-3.0'
make: *** [/home/sriram/buildroot/buildroot-2011.11/output/build/libnl-3.0/.stamp_built]
Error 2
Can anyone please help me what is going on in compilation. Do I need
to specify sysroot or path to lib.
Thanks in advance for the help.
--
Regards,
Sri.
next reply other threads:[~2012-02-19 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 16:38 Sri Ram Vemulpali [this message]
2012-02-19 21:17 ` Buildroot compilation error Sri Ram Vemulpali
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='CALyraeMK=bEVkBtbi8xAm5aWrCbjGMTkArHygG78tJ86TzzNOw@mail.gmail.com' \
--to=sri.ram.gmu06@gmail.com \
--cc=dhylands@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).