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] package: What is wrong with host-unfs3
Date: Tue, 4 Dec 2018 11:33:09 +0100	[thread overview]
Message-ID: <20181204103309.mru47cosyob5g5iq@pengutronix.de> (raw)
In-Reply-To: <CAA0ZWqY0ukRz1o6vfR7O9TDFPVUKP5pyJ7h9-baqukf1t6kjpQ@mail.gmail.com>

On Tue, Dec 04, 2018 at 10:53:52AM +0100, Andreas Friesen wrote:
> Mhhhh, sorry Michael, but PTXCONF_FIX_PERMISSIONS is not set
> 
> cat configs/platform-soc/ptxconfig | grep FIX
> # PTXCONF_FIX_PERMISSIONS is not set
> PTXCONF_BUSYBOX_CROSS_COMPILER_PREFIX=""
> PTXCONF_BUSYBOX_PREFIX="./_install"

Right, sorry, I didn't look closely enough at the error message.
You're running 'ptxdist nfsroot', right? It basically suffers from the same
issue. You'll need the commit 403d1f49c78bc484f0de036c366dfd9072725d3f
("ptxd_make_image_common: set ptx_packages_selected for image/env") for
this.
I think, in this case you can just copy the modified file
(rules/post/ptxd_make_image_common.make) into your BSP.

Michael

> Am Di., 4. Dez. 2018 um 08:36 Uhr schrieb Michael Olbrich <
> m.olbrich@pengutronix.de>:
> 
> > On Tue, Dec 04, 2018 at 12:38:00AM +0100, Andreas Friesen wrote:
> > > After BSP upgrade to 2018.11.0  I've got this error:
> > >
> > > -------------------------------
> > > target: host-unfs3.install.post
> > > -------------------------------
> > >
> > > finished target host-unfs3.install.post
> > >
> > > ptxdist: error: ethtool is not a package or not selected
> > >
> > > /usr/local/lib/ptxdist-2018.11.0/rules/post/ptxd_make_nfsd.make:12:
> > recipe
> > > for target 'ptxd_make_nfsd' failed
> > > make: *** [ptxd_make_nfsd] Error 1
> >
> > This is now fixed in master. For a workaround for the latest release see
> > my comment in the thread 'ptxdist upgrade from v2014.12.0 to latest ->
> > error'.
> >
> > Michael
> >
> > --
> > 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

> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de


-- 
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:[~2018-12-04 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 23:38 Andreas Friesen
2018-12-04  7:36 ` Michael Olbrich
2018-12-04  9:53   ` Andreas Friesen
2018-12-04 10:33     ` Michael Olbrich [this message]
2018-12-04 10:58       ` Andreas Friesen

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=20181204103309.mru47cosyob5g5iq@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