From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] libnl3 build problem: flex: fatal internal error, exec failed
Date: Wed, 25 Mar 2015 08:09:31 -0400 [thread overview]
Message-ID: <CAMwGMjztS9Pjn37G+2Hutqjs=M=y3BqGa6+WVsD+v+fKuMmpAw@mail.gmail.com> (raw)
I just updated to ptxdist-2015.03.0 as a test, and I am running into
the following error with libnl3:
----------------------
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'
GEN route/cls/ematch_grammar.c
GEN route/pktloc_syntax.c
GEN route/pktloc_grammar.c
GEN route/cls/ematch_syntax.c
flex: fatal internal error, exec failed
flex: fatal internal error, exec failed
flex: fatal internal error, exec failed
flex: fatal internal error, exec failed
make[2]: *** [route/pktloc_grammar.c] Error 141
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [route/cls/ematch_grammar.c] Error 141
make[2]: Leaving directory
`/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25'
make: *** [/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/state/libnl3.compile]
Error 2
--
ptxdist mailing list
ptxdist@pengutronix.de
reply other threads:[~2015-03-25 12:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMwGMjztS9Pjn37G+2Hutqjs=M=y3BqGa6+WVsD+v+fKuMmpAw@mail.gmail.com' \
--to=jon@ringle.org \
--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