From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] nettle build error
Date: Thu, 24 Apr 2014 01:04:56 -0400 [thread overview]
Message-ID: <CAMwGMjyZ3aH47eWZtGCZNeiQQ8ba8Rsr3nUzHBu_zagjmZwmyA@mail.gmail.com> (raw)
In-Reply-To: <CAMwGMjwy9_Bvo4hvxXmtsmsjsD2s=JgjDt-kYGYE_uARbGyd6A@mail.gmail.com>
On Wed, Apr 23, 2014 at 10:00 PM, Jon Ringle <jon@ringle.org> wrote:
> I have a ptxdist project that I recently updated from
> ptxdist-2014.02.0 to 2014.04.0. There was a version bump for nettle
> from 2.5 to 2.7.1. I am getting the following build error on nettle
> now:
Interestingly, if I run 'ptxdist images' again, nettle builds
successfully and continues on...
Jon
>
> make[3]: Entering directory
> `/home/jringle/code/ptx/ec1k-rootfs/platform-EC1K/build-target/nettle-2.7.1'
> Makefile:595: ecc-generic-modq.o.d: No such file or directory
> arm-v5te-linux-gnueabi-gcc -I. -DHAVE_CONFIG_H -g -O2 -ggdb3
> -Wno-pointer-sign -Wall -W -Wmissing-prototypes
> -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith
> -Wbad-function-cast -Wnested-externs -fpic -MT ecc-dup-jj.o -MD -MP
> -MF ecc-dup-jj.o.d -fpic -c ecc-dup-jj.c \
> && true
> make[3]: *** No rule to make target `ecc-modq.o.d'. Stop.
> make[3]: Leaving directory
> `/home/jringle/code/ptx/ec1k-rootfs/platform-EC1K/build-target/nettle-2.7.1'
> make[2]: *** [eccdata.stamp] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory
> `/home/jringle/code/ptx/ec1k-rootfs/platform-EC1K/build-target/nettle-2.7.1'
> make[1]: Leaving directory
> `/home/jringle/code/ptx/ec1k-rootfs/platform-EC1K/build-target/nettle-2.7.1'
> make[1]: *** [all] Error 2
> make: *** [/home/jringle/code/ptx/ec1k-rootfs/platform-EC1K/state/nettle.compile]
> Error 2
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-24 5:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 2:00 Jon Ringle
2014-04-24 5:04 ` Jon Ringle [this message]
2014-04-24 7:40 ` Michael Olbrich
2014-04-24 12:15 ` 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=CAMwGMjyZ3aH47eWZtGCZNeiQQ8ba8Rsr3nUzHBu_zagjmZwmyA@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