|
Message
From: Matjaz Breskvar <phoenix@o...>
Date: Sun, 26 Oct 2003 19:15:00 +0100
Subject: Re: [openrisc] or1ksim port to FreeBSD
* Matjaz Breskvar (phoenix@f...) wrote:
actually nothing. sorry ;)
> * Jure Menart (jure@k...) wrote:
> > Hi,
Hello Jure ;),
> > I made a patch, which supports building or1ksim on FreeBSD 5.x (I didn't
> > test earlier versions, but there shouldn't be any problem).
> > I don't have check in CVS permissions, so I would be really grateful if anyone
> > would take time and commit patched version of or1ksim.
> > Patch get be retrieved from:
> > http://hannanges.kom.org/stuff/freebsd_or1ksim.patch
> >
> > Changes I've made:
> > - include malloc.h changed with stdlib.h (where there isn't
> > stdlib.h included before), because FreeBSDs libc has malloc &
> > stuff now defined in stdlib.h.
> > - strndup() in peripheral/channels/ is linked with libroken (defined in
> > roken.h). All necessary checks are performed in configure process.
> > - ceil() is linked with libm (math library).
> > - few necessary #ifdef __FreeBSD__ in code
> > - xterm.c is not fully functional, I replaced on_exit() with atexit(),
> > but there is not the same functionality. For solution please, read
> > below.
> > - in testbench/ there is minor change in test script. When using
> > tail(1), I've changed "-n 2" argument to the first place after tail
> > (yes silly, but FreeBSD's getopt() demands options in the first
> > place and then other arguments). There shouldn't be any problems
> > with that on Linux systems.
> >
> > I've made a patch appliable to the todays snapshot from CVS (I've checked out
> > at about 16:30 in slovenian time).
i've taken a quick look at the patch. it's mostly build stuff, but there
are also some changes not mentioned above.
diff -bBaur or1ksim/cpu/or32/execgen.c new.or1ksim/cpu/or32/execgen.c
--- or1ksim/cpu/or32/execgen.c 2003-10-26 17:51:52.000000000 +0100
+++ new.or1ksim/cpu/or32/execgen.c 2003-10-26 17:04:54.000000000 +0100
i've taken a look into cvs and it seams that it's due to diff-ing to
an old tree. can you please confirm and update the patch accordingly.
regards,
p.
|
 |
Browse
