From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Problems building libnl3
Date: Tue, 27 Jan 2015 23:22:30 -0500 [thread overview]
Message-ID: <CAMwGMjxNEQKacK+-rHP5gC73vWJx_sLzwDkiD4_HDF4VDHxMEQ@mail.gmail.com> (raw)
In-Reply-To: <20150126134428.GA30319@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1830 bytes --]
On Mon, Jan 26, 2015 at 8:44 AM, Michael Olbrich <m.olbrich@pengutronix.de>
wrote:
> 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.
>
>
Well... When I was reproducing this before, I had tried doing a 'ptxdist
clean' and also removed all the *-dev.tar.gz packages as well and it
produced the error. Since then I had to go back to the ptxdist-14.10 that I
was using before for other work. Now I can't seem to be able to reproduce
the problem when I go to ptxdist-15.01.0. If I do get the problem again,
I'll post the info you've asked for.
Jon
[-- Attachment #1.2: Type: text/html, Size: 2427 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-01-28 4:22 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 [this message]
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=CAMwGMjxNEQKacK+-rHP5gC73vWJx_sLzwDkiD4_HDF4VDHxMEQ@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