From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Backporting udev-182 to ptxdist 1.99.20
Date: Wed, 13 Jun 2018 17:06:40 +0200 [thread overview]
Message-ID: <20180613150640.ytrryzq7caij4xzg@pengutronix.de> (raw)
In-Reply-To: <HE1PR0702MB3804D47FDBAF7FB8AEEB113C987E0@HE1PR0702MB3804.eurprd07.prod.outlook.com>
On Wed, Jun 13, 2018 at 02:57:57PM +0000, Jakov Simunic wrote:
> Hello,
> After I managed to surpass all obstacles on my way to making udev-182 build on the ancient version of ptxdist 1.99.20, there is still some work to be done 😊
> ptxdist go – does everything ok, but,
> ptxdist images – chmod and chown complain about paths to udev files
>
> chmod: cannot access `./sbin/udevd': No such file or directory
> chown: cannot access `./sbin/udevd': No such file or directory
> chmod: cannot access `./sbin/udevadm': No such file or directory
> chown: cannot access `./sbin/udevadm': No such file or directory
> chmod: cannot access `./etc/udev/rules.d/01-basic.rules': No such file or directory
> chown: cannot access `./etc/udev/rules.d/01-basic.rules': No such file or directory
> chmod: cannot access `./etc/udev/rules.d/10-local.rules': No such file or directory
> chown: cannot access `./etc/udev/rules.d/10-local.rules': No such file or directory
> chmod: cannot access `./etc/udev/rules.d/50-default.rules': No such file or directory
> chown: cannot access `./etc/udev/rules.d/50-default.rules': No such file or directory
> chmod: cannot access `./etc/init.d/udev': No such file or directory
> chown: cannot access `./etc/init.d/udev': No such file or directory
> chmod: cannot access `./etc/udev/udev.conf': No such file or directory
> chown: cannot access `./etc/udev/udev.conf': No such file or directory
> chmod: cannot access `./lib/libudev.so.0.13.1': No such file or directory
> chown: cannot access `./lib/libudev.so.0.13.1': No such file or directory
>
> What i don't understand is:
> How can i change these paths?
> Some paths seem ok, so I don't understand why chmod and chown are complaining, I suppose the path they are
I'm not sure about ptxdist 1.99.20, but in may version, this can happen
after updating packages and is usually fixed by a clean rebuilt of the
whole BSP.
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:[~2018-06-13 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 14:57 Jakov Simunic
2018-06-13 15:06 ` Michael Olbrich [this message]
2018-06-14 11:37 ` Jakov Simunic
2018-06-28 12:25 ` Jakov Simunic
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=20180613150640.ytrryzq7caij4xzg@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