Hello Hackers.
Having got to the stage of compiling successfully my second (debian) hello+fiasco+glinux set, I'm now looking at cool next step (read: "easy wins for the temporally challenged"). UX and CON seem to be my candidates.
OK, UX looks more like the world I'm used to, so I won't ask about that yet. But I /do/ have a Q. about the drops con, which has wider learning implications, so a few hints here won't go amiss.
My guess is that to yield up a con binary, I cd to l4/pkg/con, "make", and /no/ that isn't it because it falls over...
my predecessor instructions were per website, CVSco, compile hello and fiasco using gcc3.2, compile linux22 using gcc2.95.
so: how do I compile "con" and other packages, please? (or: a generalised rule to cover this) ;-)
TIA David D
Hi David!
On Sat Aug 30, 2003 at 15:04:28 +0100, David Denny wrote:
My guess is that to yield up a con binary, I cd to l4/pkg/con, "make", and /no/ that isn't it because it falls over...
If all dependencies are available a "make" in l4/pkg/con should give you a binary (see in l4/pkg/con/server/src/OBJ*/con).
It would be really helpful if you could show us the output of what's failing.
so: how do I compile "con" and other packages, please? (or: a generalised rule to cover this) ;-)
First, go to l4/ and call "make config" to configure your build environment. Then you can go to l4/pkg and call make there to build all packages which are available (checked out). If the build fails for some reason you have to resolve that. :) To start, it's probably the easiest to paste the last lines of the output here so that we can see what's going on.
Adam
l4-hackers@os.inf.tu-dresden.de