From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Problems building libnl3
Date: Mon, 26 Jan 2015 14:44:28 +0100 [thread overview]
Message-ID: <20150126134428.GA30319@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjzStEawiWfWL+Av3=-b_jhUeRSRY+4xDbN9QcT29ZqFvA@mail.gmail.com>
Hi,
On Wed, Jan 21, 2015 at 02:22:26PM -0500, Jon Ringle wrote:
> After updating to ptxdist-2015-01.0, I am having a problem build libnl3. I
> tried rebuilding host-flex, hoping this might do the trick, but it did not
> help.
> Any ideas?
>
> Jon
>
> ----------------------
> target: libnl3.compile
> ----------------------
>
> make[1]: Entering directory
> `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25'
> Making all in include
> make[2]: Entering directory
> `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25/include'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
> `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25/include'
> Making all in lib
> make[2]: Entering directory
> `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25/lib'
Is this from a clean build? I see some more stuff here:
GEN route/cls/ematch_grammar.c
GEN route/cls/ematch_syntax.c
GEN route/pktloc_grammar.c
GEN route/pktloc_syntax.c
Can you send the output from "ptxdist clean libnl3 ; ptxdist -v compile
libnl3"? Maybe we can see some more stuff there.
Michael
> make all-am
> make[3]: Entering directory
> `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25/lib'
> CC route/route_utils.lo
> CC route/route.lo
> CC route/rtnl.lo
> CC version.lo
> CC route/tc.lo
> CC route/route_obj.lo
> CC route/rule.lo
> CC route/classid.lo
> CC route/cls/fw.lo
> CC route/cls/basic.lo
> CC route/cls/cgroup.lo
> CC route/act/mirred.lo
> CC route/cls/ematch/container.lo
> CC route/cls/police.lo
> CC route/cls/u32.lo
> CC route/cls/ematch.lo
> CC route/cls/ematch/cmp.lo
> CC route/cls/ematch/nbyte.lo
> CC route/cls/ematch/meta.lo
> CC route/link/api.lo
> CC route/cls/ematch/text.lo
> route/cls/ematch.c: In function 'rtnl_ematch_parse_expr':
> route/cls/ematch.c:635:2: error: unknown type name 'YY_BUFFER_STATE'
> YY_BUFFER_STATE buf = NULL;
> ^
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-01-26 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 19:22 Jon Ringle
2015-01-26 13:44 ` Michael Olbrich [this message]
2015-01-28 4:22 ` Jon Ringle
2015-03-25 13:21 ` Jon Ringle
2015-03-26 9:23 ` Michael Olbrich
2015-03-26 10:53 ` Jon Ringle
2015-03-26 11:59 ` Jon Ringle
2015-03-27 21:52 ` Jon Ringle
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=20150126134428.GA30319@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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