Hello,
i try to build the newest snapshot while still having an old one on the disk.
Unfortunately, 'make setup' crashes when looking for Cross Tools.
Anyway, i don't think it has something to do with the new snapshot, but some hidden setup files storing my old config. Because, when i rename my old snapshot and then try to rebuild it, it crashes as well.
So, how do i make the setup really clean? 'make clean' seems not enough, since it still knows some old configs. Where are those hidden files, and how to remove them?
Thanks.
On Sun Oct 04, 2015 at 19:35:44 +0200, ba_f wrote:
i try to build the newest snapshot while still having an old one on the disk.
I.e. you use the same build directory?
Unfortunately, 'make setup' crashes when looking for Cross Tools.
How does it crash, what gets wrong? The output would be helpful for me.
Anyway, i don't think it has something to do with the new snapshot, but some hidden setup files storing my old config. Because, when i rename my old snapshot and then try to rebuild it, it crashes as well.
Tried 'make oldconfig'?
So, how do i make the setup really clean? 'make clean' seems not enough, since it still knows some old configs. Where are those hidden files, and how to remove them?
For a really fresh start, just delete the build directory and create a new one (or just delete everything therein, except the Makefile).
Adam
Am 2015-10-04 23:24, schrieb Adam Lackorzynski:
On Sun Oct 04, 2015 at 19:35:44 +0200, ba_f wrote:
i try to build the newest snapshot while still having an old one on the disk.
I.e. you use the same build directory?
Unfortunately, 'make setup' crashes when looking for Cross Tools.
How does it crash, what gets wrong? The output would be helpful for me.
Anyway, i don't think it has something to do with the new snapshot, but some hidden setup files storing my old config. Because, when i rename my old snapshot and then try to rebuild it, it crashes as well.
Tried 'make oldconfig'?
So, how do i make the setup really clean? 'make clean' seems not enough, since it still knows some old configs. Where are those hidden files, and how to remove them?
For a really fresh start, just delete the build directory and create a new one (or just delete everything therein, except the Makefile).
Adam'
Hi,
what do u mean with 'build directory'? The default build directory is l4re-snapshot/obj/ , isn't it? And this is what i use.
'make clean' already deletes l4-snapshot/obj/. clean: @$(RM) -r obj
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.
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'
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
My GCC_PATH_PREFIX=/opt/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/bin/arm-linux-gnueabihf-
Thank you.
Hi,
On Mon Oct 05, 2015 at 13:44:55 +0200, ba_f wrote:
Am 2015-10-04 23:24, schrieb Adam Lackorzynski:
On Sun Oct 04, 2015 at 19:35:44 +0200, ba_f wrote:
i try to build the newest snapshot while still having an old one on the disk.
I.e. you use the same build directory?
Unfortunately, 'make setup' crashes when looking for Cross Tools.
How does it crash, what gets wrong? The output would be helpful for me.
Anyway, i don't think it has something to do with the new snapshot, but some hidden setup files storing my old config. Because, when i rename my old snapshot and then try to rebuild it, it crashes as well.
Tried 'make oldconfig'?
So, how do i make the setup really clean? 'make clean' seems not enough, since it still knows some old configs. Where are those hidden files, and how to remove them?
For a really fresh start, just delete the build directory and create a new one (or just delete everything therein, except the Makefile).
Adam'
Hi,
what do u mean with 'build directory'? The default build directory is l4re-snapshot/obj/ , isn't it?
Yes, or the specific directory therein.
And this is what i use.
'make clean' already deletes l4-snapshot/obj/. clean: @$(RM) -r obj
Yes.
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
?
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
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
On Wed Oct 07, 2015 at 16:35:49 +0200, ba_f wrote:
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.
Thanks for the info. I tried to reproduce but had no luck. Anyway, good to know.
Adam
Am 2015-10-11 23:57, schrieb Adam Lackorzynski:
On Wed Oct 07, 2015 at 16:35:49 +0200, ba_f wrote:
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.
Thanks for the info. I tried to reproduce but had no luck. Anyway, good to know.
Adam
Ah, found the problem. I had l4re-snapshot-2014022818 in my permanent PATH. Removing this lets me build any snapshot, again.
thnx, ba_f
l4-hackers@os.inf.tu-dresden.de