Am 2015-10-06 23:44, schrieb Adam Lackorzynski:
But this cant be it. Some config stuff must be stored somewhere else.
For example, the first time i built l4re-snapshot i had to choose
between
ARM Secure World or Normal World.
When re-building the same snapshot (after 'make clean') it doesn't ask
me
for that, but the previous config is selected, already.
I'm not aware that there's user-interaction for Fiasco's configuration
when building the snapshot. I wonder how that did pop up.
Rebuilding:
'cd l4re-snapshot/'
'make clean'
'make setup'
'make'
Just to clear things up: Re-Building l4re-snapshot-2014022818 works
great.
But l4re-snapshot-2014022818_TEST does not.
'cd l4re-snapshot-2014022818/'
'make clean'
'cp -r l4re-snapshot-2014022818/ l4re-snapshot-2014022818_TEST/'
'cd l4re-snapshot-2014022818_TEST/'
'make clean'
'make setup'
'make'
So we end up with
l4re-snapshot-2014022818_TEST/l4re-snapshot-2014022818/README
l4re-snapshot-2014022818_TEST/l4re-snapshot-2014022818/bin
l4re-snapshot-2014022818_TEST/l4re-snapshot-2014022818/src
...
l4re-snapshot-2014022818_TEST/README
l4re-snapshot-2014022818_TEST/bin
l4re-snapshot-2014022818_TEST/src
etc
?
Nah.
All i wanted to say is that i copied my working snapshot (after 'make
clean') but i run into this bug when the snapshot has another name.
So i have:
$ ls
/home/imsohoteveryonejealous/l4re-snapshot-2014022818
/home/imsohoteveryonejealous/l4re-snapshot-2014022818_TEST
'make setup' always works on l4re-snapshot-2014022818, but never on
l4re-snapshot-2014022818_TEST.
>>Unfortunately, 'make setup' crashes when looking for Cross Tools.
>
>How does it crash, what gets wrong? The output would be helpful for me.
Sorry, no output here.
The CPU load just freaks out until Linux terminates the process and
reboots.
Anyway, this is what i see when manually terminating:
Checking for needed programs and tools
make ... ok
gcc ... ok
g++ ... ok
ld ... ok
gawk ... ok
perl ... ok
pkg-config ... ok
Checking for needed cross programs and tools
^CMakefile:15: recipe for target 'setup' failed
ok, so there seems to be some recursive looping which leads to this
behavior. I need to look closer at this.
Adam
Strange.
But, actually not that important.
Thnx
_______________________________________________
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
