From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] setting up opkg with ptxdist 2015.12.0
Date: Tue, 12 Jan 2016 17:21:11 +0100 [thread overview]
Message-ID: <20160112162111.GB18044@pengutronix.de> (raw)
In-Reply-To: <db60067b243d2ca15952c41db835baaf@localhost>
On Mon, Jan 11, 2016 at 01:10:32PM +0100, Alexander Dahl wrote:
> Hei hei,
>
> Am 2015-12-22 12:42, schrieb Alexander Dahl:
> >> Or go back to opkg 0.2.x?
> >
> > I copied the old rules and patches from 2015.10.0 to my BSP for now to
> > get a usable opkg. Nevertheless, help on setting up opkg or fixing it,
> > appreciated.
>
> Well, after copying the old opkg.in, opkg.make, host-opkg.in, and
> host-opkg.make to my BSP this seemed to work at first, but after a
> `ptxdist clean` I get the following error when invoking `ptxdist
> images`:
>
>
> creating index.....:
> ipkg-repository updated
> Creating ipkg index
> '/home/adahl/Work/bsp/***/platform-***/packages/Packages'...
> done.
> /home/adahl/Work/bsp/***/platform-***/sysroot-host/bin/fakeroot: line
> 21: opkg: command not found
> /usr/local/lib/ptxdist-2015.12.0/rules/post/ptxd_make_image_prepare_work_dir.make:20:
> recipe for target
> '/home/adahl/Work/bsp/***/platform-***/state/image_working_dir' failed
> make: ***
> [/home/adahl/Work/bsp/***/platform-***/state/image_working_dir] Error
> 127
>
>
> This means I have to go back to ptxdist v2015.10.0 until someone helps
> me with a solution. :-/
In the new opkg, the tool was renamed from 'opkg-cl' to 'opkg', so I
changed ptxdist accordingly. So you need to add a symlink for that in
host-opkg.install got the old opkg. Then you should be able to use the old
opkg with the latest ptxdist.
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
next prev parent reply other threads:[~2016-01-12 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 11:20 [ptxdist] [ANNOUNCE] PTXdist 2015.12.0 released Michael Olbrich
2015-12-21 18:09 ` Alexander Dahl
2015-12-22 11:42 ` [ptxdist] setting up opkg with ptxdist 2015.12.0 (Was: [ANNOUNCE] PTXdist 2015.12.0 released) Alexander Dahl
2016-01-11 12:10 ` [ptxdist] setting up opkg with ptxdist 2015.12.0 Alexander Dahl
2016-01-12 13:47 ` Tim Sander
2016-01-12 16:21 ` Michael Olbrich [this message]
2016-01-12 16:44 ` [ptxdist] setting up opkg with ptxdist 2015.12.0 (Was: [ANNOUNCE] PTXdist 2015.12.0 released) Michael Olbrich
2016-01-12 16:31 ` [ptxdist] [ANNOUNCE] PTXdist 2015.12.0 released Michael Olbrich
2016-08-02 8:44 ` Alexander Dahl
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=20160112162111.GB18044@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