From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Tim Sander <tim@krieglstein.org>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] "ptxdist get" failure in container
Date: Fri, 27 Jan 2023 17:09:47 +0100 [thread overview]
Message-ID: <20230127160947.GB8218@pengutronix.de> (raw)
In-Reply-To: <4457593.LvFx2qVVIh@sanderhbk>
On Fri, Jan 27, 2023 at 04:34:50PM +0100, Tim Sander wrote:
> I have the problem that when i run "ptxdist-2023.01.0 get" in a container
> environment i get the following output:
> ptxdist-2023.01.0 -d -d -d -d -d -d -d -d -d -v -v -v -v -v -v get
> GNU Make 4.3
> Built for x86_64-pc-linux-gnu
> Copyright (C) 1988-2020 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Reading makefiles...
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> make: -c: No such file or directory
> Updating makefiles....
> Updating goal targets....
> File 'get' does not exist.
> File '/downloads/sources/ethtool-6.0.tar.xz' does not exist.
> Must remake target '/downloads/sources/ethtool-6.0.tar.xz'.
> make: -c: No such file or directory
> make: *** [/usr/lib/ptxdist-2023.01.0/rules/post/ptxd_make_world_get.make:15:
> /downloads/sources/ethtool-6.0.tar.xz] Error 127
>
> I have not found the reason for this error, but i know that the same call
> works with the same call on my developer machine. So it must be some difference
> in the environment. I checked for various different missing executables (e.g.
> gawk) but found nothing? Any idea what might be amiss?
I'm guessing that there the actual command comes from a variable that is
empty. Can you run:
strace -eexecve -f -o logfile.txt ptxdist-2023.01.0 get
and take a look at logfile.txt. You should find the '-c' there as failed
commands. Maybe the other arguments will give as a hint what fails here.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-01-27 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 15:34 Tim Sander
2023-01-27 16:09 ` Michael Olbrich [this message]
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=20230127160947.GB8218@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=tim@krieglstein.org \
/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