[Developer] x86_64 and g++

Jorge Torres jorge.torres.maldonado at gmail.com
Mon Apr 30 03:04:45 EST 2007


Hi Ernesto,

Actually QEMU works fine for me,

Try this:

qemu -hda c.img -nographic

if you want network too:

qemu -hda build/c.img -net nic -net tap -nographic

Hope it helps,


Jorge
On 4/28/07, Ernesto Bascon <ebasconp at gmail.com> wrote:
>
> Excuse my ignorance, but,
>
> when I do a tools/build.py; I get a c.img file.
>
> What simulator can I use to boot from that c.img? I tried on QEMU and
> had no success.
>
> Regards,
>
>
> Ernesto.
>
> On 28/04/07, Ernesto Bascon <ebasconp at gmail.com> wrote:
> > The toolchain provided by Hal and Jorge's Torres were quite helpful,
> >
> > thanks a lot.
> >
> > On 27/04/07, Jorge Torres <jorge.torres.maldonado at gmail.com> wrote:
> > > HI,
> > >
> > > I had the same problem, but It was because I was using gcc-4.1 not
> > > gcc-3.3and g++-
> > > 3.3
> > >
> > > Solution (debian):
> > > apt-get install gcc-3.3
> > > apt-get install g++-3.3
> > >
> > > then for OKL4 you should use the toolsuffix flag for buld.py script,
> like
> > > this:
> > > ./tools/build.py machine=ia32_pc99 project=iguana wombat=True
> toolsuffix=-
> > > 3.3
> > >
> > > Hope it helps,
> > >
> > >
> > > Jorge
> > >
> > > On 4/27/07, Carl van Schaik <carl.vanschaik at gmail.com> wrote:
> > > >
> > > > glee wrote:
> > > > > On Thu, Apr 26, 2007 at 11:36:43PM -0400, Ernesto Bascon wrote:
> > > > >
> > > > >> Hi okl4 guys:
> > > > >>
> > > > >> I have two questions:
> > > > >>
> > > > >> 1. I have a x86_64 machine running kubuntu 6.10 and was
> unsuccessful
> > > > >> to build Wombat on my machine.  My compiler is gcc-4.1.1.
> > > > >>   1. 1. With machine = ia32_pc99  I got:
> > > > >>
> > > > >>
> > > > >
> > > > > Try tweaking it and compiling with -m32.  your compiler probably
> > > > > compiles 64-bit code by default.  I sometimes find commenting the
> > > > > self.dict["CXXCOMSTR"] (for C++, similar for C and assembly)
> helpful
> > in
> > > > > trying to find out what exact flags the build system is passing to
> the
> > > > > compiler or assembler.
> > > > >
> > > > Easer just to add "verbose_str=1" to the build command line. ie:
> > > > ./tools/build.py machine=... ....  verbose_str=1
> > > >
> > > > >
> > > > >> fenizios at Eia:~/okl4_release_1.4.1.1$ ./tools/build.py
> > > > >> machine=ia32_pc99 project=iguana wombat=True simulate
> > > > >> scons: Reading SConscript files ...
> > > > >> scons: done reading SConscript files.
> > > > >> scons: Building targets ...
> > > > >> [CXX ] build/pistachio/object/pistachio/src/cache.o
> > > > >> /tmp/ccxTWtsd.s: Assembler messages:
> > > > >> /tmp/ccxTWtsd.s:41: Error: suffix or operands invalid for `mov'
> > > > >> /tmp/ccxTWtsd.s:42: Error: Incorrect register `%rbp' used with
> `l'
> > > > suffix
> > > > >> /tmp/ccxTWtsd.s:107: Error: suffix or operands invalid for `mov'
> > > > >> /tmp/ccxTWtsd.s:108: Error: Incorrect register `%rax' used with
> `l'
> > > > suffix
> > > > >> /tmp/ccxTWtsd.s:171: Error: suffix or operands invalid for `mov'
> > > > >> /tmp/ccxTWtsd.s:172: Error: Incorrect register `%r8' used with
> `l'
> > > > suffix
> > > > >> /tmp/ccxTWtsd.s:220: Error: suffix or operands invalid for `mov'
> > > > >> /tmp/ccxTWtsd.s:221: Error: Incorrect register `%rax' used with
> `l'
> > > > suffix
> > > > >> scons: *** [build/pistachio/object/pistachio/src/cache.o] Error 1
> > > > >>
> > > > >>   1.2. With machine=pc99_64 I got:
> > > > >>
> > > > >> fenizios at Eia:~/okl4_release_1.4.1.1$ ./tools/build.py
> machine=pc99_64
> > > > >> project=iguana wombat=True simulate
> > > > >> scons: Reading SConscript files ...
> > > > >> architecture x86_64 is not yet supported by atomic_ops.
> supported:
> > > > >> ['arm', 'ia32']
> > > > >> /home/fenizios/okl4_release_1.4.1.1/pistachio/SConscript:84
> > init32.cc
> > > > >> not found for x86_64
> > > > >>
> > > > >> so, how can I build Wombat on a x86_64 box? (I tried compiling
> > > > >> ia32_pc99 on NetBSD 3.1 for AMD64 and got the same assembler
> errors).
> > > > >>
> > > > >>
> > > > >> 2. Kenge provides a libc implementation for writing C programs on
> top
> > > > >> of L4; do you provide the standard C++ library too?
> > > > >>
> > > > >> If yes, how can I build a program using it?
> > > > >> If no, what do you think that must be done to support C++
> > > > implementations?
> > > > >>
> > > > >>
> > > > >
> > > > > I do not think it currently has a standard C++ library.  It may be
> > > > > possible to port an existing one.  On Wombat however, you
> > > > > can of course run C++ applications.
> > > > >
> > > > >
> > > > >
> > > > >> Regards,
> > > > >>
> > > > >>
> > > > >> Ernesto
> > > > >>
> > > > >
> > > > >        - gl
> > > > >
> > > > >> _______________________________________________
> > > > >> Developer mailing list
> > > > >> Developer at okl4.org
> > > > >> https://lists.okl4.org/mailman/listinfo/developer
> > > > >>
> > > > >>
> > > > >
> > > > > _______________________________________________
> > > > > Developer mailing list
> > > > > Developer at okl4.org
> > > > > https://lists.okl4.org/mailman/listinfo/developer
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Developer mailing list
> > > > Developer at okl4.org
> > > > https://lists.okl4.org/mailman/listinfo/developer
> > > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20070429/858cb2ef/attachment.htm 


More information about the Developer mailing list