Hi,
I'm working on a port of gnumach-oskit to alpha, and I'm trying to
build a gnumach-oskit kernel (downloaded from CVS yesterday), but I'm
getting a linker error on the last two steps of the build (the final two
links), and I was wondering if anyone had seen this or had any ideas
about
I'm trying to cross-compile libc, and the build itself works, but the
install fails in the "manual" directory (something about a missing or
broken link with libc.texi).
I was getting this error from cvs a week or two ago, and I deleted my
local tree and re-got an entirely new tree yesterday, b
Hi,
With much help from Roland McGrath, I have a (mostly) complete set of
cross-compiler tools (host=alpha-linux, build=alpha-linux,
target=alpha-gnu) in place, but I am having problems getting
gnumach-oskit to compile.
I tried the following:
cd gnumach-oskit
>
>
>>Also, should anything specific need to be done to support a target
>>of a different architecture target for the HURD (i.e., alpha-gnu),
>>and if so, what?
>>
>
>I've never tried this, but here's a quick brainstorm of pieces you
>might have to touch:
>
>1) Gcc, to tell it that alpha-*-gnu is
I have tried to follow the instructions for building a cross-compiler from
the HURD homepage, but I tried to download the lastest (3.0.4) instead of
2.95.2, and I can find no reference anywhere (in the config* files, either
in the 2.95.2 or the 3.0.4 gcc source) to building the HURD as a target
($
Has anyone been able to build the GNU Mach-OSKit kernel since about 2pm MST
yesterday?
Trying to do a "make all" I am getting the following failure:
make: *** No rule to make target `kernel'. Stop.
I checked gnumach/Makefile and gnumach/Makefile.in, but neither list a
target for "kernel" (
All,
I'm trying to figure-out exactly how to build the oskit-branch version
of GNU Mach with OSKit, but I'm not quite sure how the two are supposed to
fit together (I've got OSKit building, but now what do I do so that GNU Mach
can finish compiling?)
I was referred to www.etherhogz.org,
> The oskit is a set of libraries that provide stuff you might want to use
in
> a kernel, and the direction we are moving is to use oskit libraries to do
> everything that they are useful for when it can replace old CMU code. The
> oskit is not useful for anything on Alpha at the moment, so there
> Please tell us all the details you can about exactly which version of the
> CMU Alpha port code you got from where.
I _believe_ it is the old version 2.5 source (by 3.0, support seems to have
been dropped)...
> As to the oskit-mach issue, I'd say you should just stick with what you
are
> doi
> You can get the OSKit version of gnumach by checking out the
> oskit branch (-r oskit-branch) of gnumach. You can get the OSKit at
> http://www.cs.utah.edu/flux/oskit/.
I got the oskit-branch version of gnumach, but it seems to be incomplete
(the build complains about a bunch of oskit files th
> > I have completed a very initial (it compiles but does not yet boot)
port
> > of GNU Mach to the Alpha processor--would anyone be willing to review
and
> > submit this patch?
>
> I've not downloaded the patch yet, but do you know we are going to
> switch to the OSKit version of gnumach soon
All,
I have completed a very initial (it compiles but does not yet boot) port
of GNU Mach to the Alpha processor--would anyone be willing to review and
submit this patch?
This patch does not affect any x86 files or directories--it merely adds
the necessary Alpha-specific directories (and
12 matches
Mail list logo
