Hello,
Recent updates to Debian Unstable seem to be causing a few minor build problems in Genode. Automake being updated from 1.15 to 1.16 was simple to solve, but I have another problem that I'm not sure how to solve.
Depending of whether I'm building a disk image or an ISO, I get one of the following errors:
Error: 'e2mkdir' command could be not found.
or:
Error: 'xorriso' command could be not found.
But both of those commands are available, and worked up until recently.
Does anyone have any thoughts on what might cause this?
Thanks!
Error: 'e2mkdir' command could be not found.
or:
Error: 'xorriso' command could be not found.
But both of those commands are available, and worked up until recently.
Does anyone have any thoughts on what might cause this?
On the one-in-ten (low) odds that this could help :
Could it be a "root" vs "not root" ownership problem ? What does "ls -l" of said commands tell, re. their group/world/user access rights. Last week I saw a ticket on a mailling-list re. a similar problem, a command that "no longer worked" after a linux upgrade, despite working ok when called from a terminal (ended up being, because said Terminal was "root" so had the creds to access the command, or the command had the "s" bit or whatever).
Cedric
Hi John,
On 03.12.21 16:45, John J. Karcher wrote:
Recent updates to Debian Unstable seem to be causing a few minor build problems in Genode. Automake being updated from 1.15 to 1.16 was simple to solve, but I have another problem that I'm not sure how to solve.
Depending of whether I'm building a disk image or an ISO, I get one of the following errors:
Error: 'e2mkdir' command could be not found.
or:
Error: 'xorriso' command could be not found.
But both of those commands are available, and worked up until recently.
I have the faint suspicion that this may be related to [1].
[1] https://github.com/genodelabs/genode/issues/4319
The issue was presumably fixed by [2] but maybe one remaining use of 'which' slipped through?
[2] https://github.com/genodelabs/genode/commit/4cfd954e1e56900ee42adf8d815a39f0...
Cheers Norman
Thanks Cedric and Norman for the suggestions . . .
On 12/4/21 04:02, Norman Feske wrote:
Hi John,
On 03.12.21 16:45, John J. Karcher wrote:
Recent updates to Debian Unstable seem to be causing a few minor build problems in Genode. Automake being updated from 1.15 to 1.16 was simple to solve, but I have another problem that I'm not sure how to solve.
Depending of whether I'm building a disk image or an ISO, I get one of the following errors:
Error: 'e2mkdir' command could be not found.
or:
Error: 'xorriso' command could be not found.
But both of those commands are available, and worked up until recently.
I have the faint suspicion that this may be related to [1].
[1] https://github.com/genodelabs/genode/issues/4319
The issue was presumably fixed by [2] but maybe one remaining use of 'which' slipped through?
[2] https://github.com/genodelabs/genode/commit/4cfd954e1e56900ee42adf8d815a39f0...
Interestingly, it was related to this, but there is another facet that I don't understand.
First, line 550 of "tool/run/run" still contained a "which" command, which I changed to:
if { [catch {set path [exec command -v $command]}] == 0} {
Running "command -v e2mkdir" gives "/usr/bin/e2mkdir", so I expected this change to fix the problem, but it didn't.
Changing line 554 of the same file to manually look in "/usr/bin" did work:
set dir { /sbin /usr/sbin /usr/local/bin /usr/bin }
I don't know why the second change is necessary, but it works, so I'm not complaining. :^)
Thanks again!
John J. Karcher devuser@alternateapproach.com
Hi John,
On Sun, Dec 05, 2021 at 23:00:21 CET, John J. Karcher wrote:
First, line 550 of "tool/run/run" still contained a "which" command, which I changed to:
if { [catch {set path [exec command -v $command]}] == 0} {
Running "command -v e2mkdir" gives "/usr/bin/e2mkdir", so I expected this change to fix the problem, but it didn't.
This is because the exec aborts with an error.
tclsh> exec command -v xorriso couldn't execute "command": no such file or directory while evaluating {exec command -v xorriso} tclsh> exec bash -c "command -v xorriso" /usr/bin/xorriso tclsh>
"command" is an bash built-in command and can't be executed by Tcl/Expect directly. With the following small change to the line above your second patch is unnecessary.
if { [catch {set path [exec bash -c "command -v $command"]}] == 0} {
Regards
On 12/6/21 02:41, Christian Helmuth wrote:
Hi John,
On Sun, Dec 05, 2021 at 23:00:21 CET, John J. Karcher wrote:
First, line 550 of "tool/run/run" still contained a "which" command, which I changed to:
if { [catch {set path [exec command -v $command]}] == 0} {
Running "command -v e2mkdir" gives "/usr/bin/e2mkdir", so I expected this change to fix the problem, but it didn't.
This is because the exec aborts with an error.
tclsh> exec command -v xorriso couldn't execute "command": no such file or directory while evaluating {exec command -v xorriso} tclsh> exec bash -c "command -v xorriso" /usr/bin/xorriso tclsh>
"command" is an bash built-in command and can't be executed by Tcl/Expect directly. With the following small change to the line above your second patch is unnecessary.
if { [catch {set path [exec bash -c "command -v $command"]}] == 0} {
That solved it. I knew it was a silly problem. :^)
Thanks!
John J. Karcher devuser@alternateapproach.com
Hi John,
"command" is an bash built-in command and can't be executed by Tcl/Expect directly. With the following small change to the line above your second patch is unnecessary.
if { [catch {set path [exec bash -c "command -v $command"]}] == 0} {
That solved it. I knew it was a silly problem. :^)
could you please give commit [1] a try? The solution is a little bit leaner.
[1] https://github.com/nfeske/genode/commit/b5a604f2463862acc0766090e66e04580fad...
Cheers Norman
On 12/15/21 09:38, Norman Feske wrote:
Hi John,
"command" is an bash built-in command and can't be executed by Tcl/Expect directly. With the following small change to the line above your second patch is unnecessary.
if { [catch {set path [exec bash -c "command -v $command"]}] == 0} {
That solved it. I knew it was a silly problem. :^)
could you please give commit [1] a try? The solution is a little bit leaner.
[1] https://github.com/nfeske/genode/commit/b5a604f2463862acc0766090e66e04580fad...
Leaner and cleaner. And works like a charm!
Thanks again!
John J. Karcher devuser@alternateapproach.com
-
Christian Helmuth -
John J. Karcher -
Norman Feske -
ttcoder＠netcourrier.com