I have not been able to install from
l4re-snapshot-2013123021.tar.bz2
The toolchain test says everything is fine (though I had to install dialog and doxygen from the repos as well).
With 'make setup' I get the dialog, and I can pick between x86-32 (ia32), UX-32, or amd64/x86_64 (or arm, though I didn't test that).
I have a 64-bit CPU but it runs a 32-bit Debian Linux.
What happens next is whatever I pick, I get l4/, l4linux/, and fiasco/ in obj/.
It says I should set the PATH to include bin/, but except for the arm stuff, there is only setup.d/04-setup there to execute (is that it?). Anyway, I did that, and on 'make' it says:
make[1]: Entering directory `/home/incal/core/l4re-snapshot-2013123021' =============== Building all Fiasco configurations ============ =============== Building all L4Re configurations ============ =============== Building all L4Linux configurations =========== =============== Building Image ================================ =============== Build done ==================================== make[1]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021'
However, as there is nothing in those directories, nothing happens.
Hi,
On Thu Jan 30, 2014 at 19:12:27 +0100, Emanuel Berg wrote:
I have not been able to install from
l4re-snapshot-2013123021.tar.bz2
The toolchain test says everything is fine (though I had to install dialog and doxygen from the repos as well).
With 'make setup' I get the dialog, and I can pick between x86-32 (ia32), UX-32, or amd64/x86_64 (or arm, though I didn't test that).
I have a 64-bit CPU but it runs a 32-bit Debian Linux.
What happens next is whatever I pick, I get l4/, l4linux/, and fiasco/ in obj/.
It says I should set the PATH to include bin/, but except for the arm stuff, there is only setup.d/04-setup there to execute (is that it?). Anyway, I did that, and on 'make' it says:
Setting this path up is basically only needed for having the ARM cross compiler, so can be omitted if you're just interested in x86.
make[1]: Entering directory `/home/incal/core/l4re-snapshot-2013123021' =============== Building all Fiasco configurations ============ =============== Building all L4Re configurations ============ =============== Building all L4Linux configurations =========== =============== Building Image ================================ =============== Build done ==================================== make[1]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021'
However, as there is nothing in those directories, nothing happens.
You say you have an obj dir, which is good. What's in there? There should be a Fiasco build directory (such as obj/fiasco/ia32), l4re build dir (obj/l4/x86) and an L4Linux build dir (obj/l4linux). Are those dirs there for you?
Adam
Adam Lackorzynski adam@os.inf.tu-dresden.de writes:
Setting this path up is basically only needed for having the ARM cross compiler, so can be omitted if you're just interested in x86.
OK, good to know, thank you.
You say you have an obj dir, which is good. What's in there? There should be a Fiasco build directory (such as obj/fiasco/ia32), l4re build dir (obj/l4/x86) and an L4Linux build dir (obj/l4linux). Are those dirs there for you?
No, that's why I said that, because the
for f in obj/fiasco/*; do for f in obj/l4/*; do for f in obj/l4linux/*; do
stuff in the Makefile won't do anything if those dirs are empty.
The only thing in obj/, except for those three empty subdirs, is .config, which contains:
# snapshot build configuration
I'll try to create the subdirs manually and see what happens.
Adam Lackorzynski adam@os.inf.tu-dresden.de writes:
You say you have an obj dir, which is good. What's in there? There should be a Fiasco build directory (such as obj/fiasco/ia32), l4re build dir (obj/l4/x86) and an L4Linux build dir (obj/l4linux). Are those dirs there for you?
I tried to 'make' after setting the subdirs up manually (the ia32 and x86). Here is what it says, having run it once for each dir:
make[1]: Entering directory `/home/incal/core/l4re-snapshot-2013123021' =============== Building all Fiasco configurations ============ ============ Building in obj/fiasco/ia32 ========= make[2]: Entering directory `/home/incal/core/l4re-snapshot-2013123021/obj/fiasco/ia32' make[2]: *** No targets specified and no makefile found. Stop. make[2]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021/obj/fiasco/ia32' Error building the Fiasco 'obj/fiasco/ia32' variant. Press RETURN to continue with other variants. /bin/sh: 8: read: arg count make[1]: *** [build_all] Error 2 make[1]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021' make: *** [all] Error 2
make[1]: Entering directory `/home/incal/core/l4re-snapshot-2013123021' =============== Building all Fiasco configurations ============ =============== Building all L4Re configurations ============ ============ Building in obj/l4/x86 ========= make[2]: Entering directory `/home/incal/core/l4re-snapshot-2013123021/obj/l4/x86' make[2]: *** No targets specified and no makefile found. Stop. make[2]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021/obj/l4/x86' Error building the L4Re 'obj/l4/x86' variant. Press RETURN to continue with other variants. /bin/sh: 8: read: arg count make[1]: *** [build_all] Error 2 make[1]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021' make: *** [all] Error 2
Hi,
Am 30.01.2014 19:12, schrieb Emanuel Berg:
I have not been able to install from
l4re-snapshot-2013123021.tar.bz2
The toolchain test says everything is fine (though I had to install dialog and doxygen from the repos as well).
With 'make setup' I get the dialog, and I can pick between x86-32 (ia32), UX-32, or amd64/x86_64 (or arm, though I didn't test that).
I have a 64-bit CPU but it runs a 32-bit Debian Linux.
What happens next is whatever I pick, I get l4/, l4linux/, and fiasco/ in obj/.
It is not sufficent to use the cursor keys only to pick an item. You must also press the space bar once on the desired targets and asterisk the item prior proceeding with OK.
It says I should set the PATH to include bin/, but except for the arm stuff, there is only setup.d/04-setup there to execute (is that it?). Anyway, I did that, and on 'make' it says:
make[1]: Entering directory `/home/incal/core/l4re-snapshot-2013123021' =============== Building all Fiasco configurations ============ =============== Building all L4Re configurations ============ =============== Building all L4Linux configurations =========== =============== Building Image ================================ =============== Build done ==================================== make[1]: Leaving directory `/home/incal/core/l4re-snapshot-2013123021'
However, as there is nothing in those directories, nothing happens.
Yes, you did not select anything, so nothing will be built :-)
Martin.
It is not sufficent to use the cursor keys only to pick an item. You must also press the space bar once on the desired targets and asterisk the item prior proceeding with OK.
Like I said, I had to *install* dialog...
While I think a CLI is better (dialog doesn't play well with tmux if the dialog doesn't fit the pane), if you insist, a good idea would be to change the message following "OK" if nothing is selected because now you get the impression something happened (apart from a couple of near-empty dirs), and the note about PATH intones that.
But thank you, that was it, it now works.
On Mon Feb 03, 2014 at 18:07:29 +0100, Emanuel Berg wrote:
It is not sufficent to use the cursor keys only to pick an item. You must also press the space bar once on the desired targets and asterisk the item prior proceeding with OK.
Like I said, I had to *install* dialog...
While I think a CLI is better (dialog doesn't play well with tmux if the dialog doesn't fit the pane), if you insist, a good idea would be to change the message following "OK" if nothing is selected because now you get the impression something happened (apart from a couple of near-empty dirs), and the note about PATH intones that.
Good idea, I've added a check for that situation.
Thanks, Adam
l4-hackers@os.inf.tu-dresden.de