mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Problems building libnl3
Date: Thu, 26 Mar 2015 10:23:59 +0100	[thread overview]
Message-ID: <20150326092359.GX3000@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjx2DhXzv7ap9m0em5xZcT-c26wjRdvnn5wfmN_x8rBGQQ@mail.gmail.com>

On Wed, Mar 25, 2015 at 09:21:32AM -0400, Jon Ringle wrote:
> On Tue, Jan 27, 2015 at 11:22 PM, Jon Ringle <jon@ringle.org> wrote:
> > On Mon, Jan 26, 2015 at 8:44 AM, Michael Olbrich <m.olbrich@pengutronix.de>
> > wrote:
> >> 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.
> 
> $ ptxdist clean libnl3 ; ptxdist -v compile libnl3
[...]
> ptxdist: executing:
> PATH=/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/sysroot-cross/bin:/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/sysroot-cross/sbin:\/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/sysroot-host/lib/wrapper:/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/sysroot-host/bin:/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/sysroot-host/sbin:/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/selected_toolchain:/usr/local/lib/ptxdist-2015.03.0_GP/bin:/home/local/GRIDPOINT/jringle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/OSELAS.Toolchain-2013.12.1/arm-v5te-linux-gnueabi/gcc-4.8.2-glibc-2.18-binutils-2.24-kernel-3.12-sanitized/bin:/opt/arm-2009q1/bin
[...]
> make[2]: Entering directory
> `/home/local/GRIDPOINT/jringle/code/gpec/ec1k-rootfs/platform-EC1K/build-target/libnl-3.2.25/lib'
> /usr/local/lib/ptxdist-2015.03.0_GP/bin/mkdir -p route/cls; flex
> --header-file=route/cls/ematch_grammar.h  -o
> route/cls/ematch_grammar.c route/cls/ematch_grammar.l
> /usr/local/lib/ptxdist-2015.03.0_GP/bin/mkdir -p route/cls; bison -y
> -d  -o route/cls/ematch_syntax.c route/cls/ematch_syntax.y
> /usr/local/lib/ptxdist-2015.03.0_GP/bin/mkdir -p route; flex
> --header-file=route/pktloc_grammar.h  -o route/pktloc_grammar.c
> route/pktloc_grammar.l
> /usr/local/lib/ptxdist-2015.03.0_GP/bin/mkdir -p route; bison -y -d
> -o route/pktloc_syntax.c route/pktloc_syntax.y
> flex: fatal internal error, exec failed
> flex: fatal internal error, exec failed

If I read the code correctly, then flex is trying to execute 'm4' here.
Maybe that's missing?

Michael

> make[2]: *** [route/pktloc_grammar.c] Error 141
> make[2]: *** Waiting for unfinished jobs....
> flex: fatal internal error, exec failed
> flex: fatal internal error, exec failed
> 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

-- 
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

  reply	other threads:[~2015-03-26  9:24 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
2015-01-28  4:22   ` Jon Ringle
2015-03-25 13:21     ` Jon Ringle
2015-03-26  9:23       ` Michael Olbrich [this message]
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=20150326092359.GX3000@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