headers
Marcus Brinkmann | 1 Mar 14:26
Picon
Favicon

Re: No luck with libc compilation - missing l4/arch.h file (?)

At Thu, 24 Feb 2005 10:55:44 +0100,
Bas Wijnen <shevek <at> fmf.nl> wrote:
> > Sure.  If you really want to get us ahead of where we have already
> > been a zillion times though, it would be nice if you could work out
> > how to get proper "make install-header" targets with automake, so that
> > we can have a clean and proper bootstrap procedure without dirty tricks.
> > It can't be much that is required to get this working properly.
> 
> Sounds good, but I don't know much about autotools.  Perhaps this is a
> good time to learn about them. :-)

Yes, indeed :)

> >>Also, there should be a
> >>note about linking the include and library files.
> >
> > I hope I have made sufficiently clear why there should not be such a note.
> 
> Well, at the moment the absense of a note suggests that everything
> works.

You mean, like with the absence of source code? :) Mmh, there is
something true with that.  Code that doesn't exist can't be broken...

Thanks,
Marcus
Permalink | Reply | 0 comments |
headers
B. Douglas Hilton | 2 Mar 14:07
Picon

Re: No luck with libc compilation - missing l4/arch.h file (?)

Marcus Brinkmann wrote:

>Sure.  If you really want to get us ahead of where we have already
>been a zillion times though, it would be nice if you could work out
>how to get proper "make install-header" targets with automake, so that
>we can have a clean and proper bootstrap procedure without dirty tricks.
>It can't be much that is required to get this working properly.
>
I am also running into the arch.h issues while attempting to build libc 
for hurd-l4, and I am considering working on building the 
cross-toolchain environment (I'm in Gentoo now so I don't have the cheap 
cross-compiler anymore). But anyways, I read your message above and 
figured I'd take a crack at the install-headers target and here's how I 
approached it.

Insert this into configure.am before the documentation checks:

# Required for making the install-headers target
AC_CHECK_PROG([CP], [cp], cp :)

Then append the following to the top level Makefile.am:

install-headers: include
    $(CP) -RL include $(prefix)

include: config.status
    ./config.status

It is sort of a kludge but it gets the job done. The main problem is 
that the source include directory doesn't even exist until you run
(Continue reading)

Permalink | Reply | 1 comment |
headers
Martin Schaffner | 2 Mar 18:01
Picon

Re: No luck with libc compilation - missing l4/arch.h file

B. Douglas Hilton wrote:

> I was thinking about the cross-compiler issues for l4-hurd, and I
> remember a ways back in this thread somebody mentioned MIG. Now, IIRC,
> you can't make a --target=i686-gnu compiler unless you have both Mach
> and MIG headers installed, neither of which is needed by l4-hurd, so
> this doesn't look to be a good way to go about this.
>
> I think that updating the make-cross script might be the preferred
> solution, and if somebody could point me to or send me a recent version
> of the script I wouldn't mind looking it over.

There exists a very comfortable way of creating a cross-compiler that 
targets *-linux-gnu, which works with recent versions of gcc and glibc, 
which might be adapted to be able to target *-gnu as well:

http://kegel.com/crosstool/
Permalink | Reply | 0 comments |
headers
B. Douglas Hilton | 2 Mar 15:54
Picon

Re: No luck with libc compilation - missing l4/arch.h file (?)

I was thinking about the cross-compiler issues for l4-hurd, and I 
remember a ways back in this thread somebody mentioned MIG. Now, IIRC, 
you can't make a --target=i686-gnu compiler unless you have both Mach 
and MIG headers installed, neither of which is needed by l4-hurd, so 
this doesn't look to be a good way to go about this.

I think that updating the make-cross script might be the preferred 
solution, and if somebody could point me to or send me a recent version 
of the script I wouldn't mind looking it over.
Permalink | Reply | 501 comments |
headers
Christophe Devine | 2 Mar 20:46

Re: Once more: Hurd-L4 ISOs

Dmitrij D. Czarkoff wrote:

> Are there any ISOs with Hurd-L4? If there are any, where can they be
> downloaded from. If they are not, is anyone planning to create them?

A bootable iso image is available at http://gnuppix.org/

--

-- 
Christophe Devine
Permalink | Reply | 501 comments |
headers
Christophe Devine | 2 Mar 21:46

Re: Once more: Hurd-L4 ISOs

Alfred M. Szmidt <ams <at> kemisten.nu> wrote:

> "The Gnuppix project provides a bootable CD with a full-featured
> GNU/Hurd system, running on top of the L4 microkernel."
> 
> This is false, no full featured GNU/Hurd system exists that runs under
> L4.

Well, that's the goal we hope to reach one day :-) Anyway, I rephrased
that sentence.

--

-- 
Christophe Devine
Permalink | Reply | 0 comments |
headers
Alfred M. Szmidt | 2 Mar 21:35
Picon

Re: Once more: Hurd-L4 ISOs

   A bootable iso image is available at http://gnuppix.org/

"The Gnuppix project provides a bootable CD with a full-featured
GNU/Hurd system, running on top of the L4 microkernel."

This is false, no full featured GNU/Hurd system exists that runs under
L4.
Permalink | Reply | 501 comments |
headers
Marcus Brinkmann | 3 Mar 02:36
Picon
Favicon

Re: No luck with libc compilation - missing l4/arch.h file (?)

At Wed, 02 Mar 2005 08:07:31 -0500,
"B. Douglas Hilton" <b.d.hilton <at> verizon.net> wrote:
> # Required for making the install-headers target
> AC_CHECK_PROG([CP], [cp], cp :)

There is $(INSTALL_HEADER) defined by automake.

There is also $(HEADERS).

And there are targets like "install-includehurdHEADERS" which are run
by targets like "install-data-am" and "install-data".

Actually, install-data is supposed to be platform independent, which
header files generally are not, so it is kind of bogus to have the
header files installed by install-data.  But anyway, maybe
"install-data" is already good enough, if you can run it without
building anything.  Maybe you can check this out?

For the cleanest solution (or if install-data doesn't work), I would
really like to see an install-header target supported natively by
automake.

> Then append the following to the top level Makefile.am:
> 
> install-headers: include
>     $(CP) -RL include $(prefix)
> 
> include: config.status
>     ./config.status
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marcus Brinkmann | 3 Mar 03:12
Picon
Favicon

Re: No luck with libc compilation - missing l4/arch.h file (?)

At Wed, 02 Mar 2005 09:54:57 -0500,
"B. Douglas Hilton" <b.d.hilton <at> verizon.net> wrote:
> 
> I was thinking about the cross-compiler issues for l4-hurd, and I 
> remember a ways back in this thread somebody mentioned MIG. Now, IIRC, 
> you can't make a --target=i686-gnu compiler unless you have both Mach 
> and MIG headers installed, neither of which is needed by l4-hurd, so 
> this doesn't look to be a good way to go about this.

I think you recall incorrectly.  It is true that you can't make a full
gcc compile without libc.  libgcc2.a will fail, not to talk about all
those other language supports but C.  So, there is some kludgery still
involved.  But I don't think Mach or mig are involved at all.

> I think that updating the make-cross script might be the preferred 
> solution, and if somebody could point me to or send me a recent version 
> of the script I wouldn't mind looking it over.

Well, let's say you use make-cross or a similar hack.  That does only
change what you do to get i686-gnu-gcc.  It has no relevance on any
particular step in the bootstrapping procedure otherwise.  All
the other issues (except how to get a cross compiler) will still be
the same.

INSTALL-cross contains all the important steps, although the details
may be out of date.  Alfred posted some updated version of it on
bug-hurd recently.  But in the end, it's always the same.  Let me try
to give a summary for both Hurd on Mach and Hurd on L4:

1. Compile binutils and some sort of gcc.
(Continue reading)

Permalink | Reply | 501 comments |
headers
Neal H. Walfield | 3 Mar 17:57

Re: multiple capabilities in a single RPC

Marcus,

Based on our previous emails, here is a new implementation of
hurd_cap_ctx_start_cap_use.  This is just ctx-cap-use.c; I haven't
included the changes for cap-server.h, etc.

Please let me know what you think, I depend on this functionality for
my current work on physmem (specifically hurd_pm_container_map).

Thanks,
Neal

/* ctx-cap-use.c - Use capabilities within an RPC context.
   Copyright (C) 2005 Free Software Foundation, Inc.
   Written by Marcus Brinkmann <marcus <at> gnu.org>

   This file is part of the GNU Hurd.

   This program is free software; you can redistribute it and/or
   modify it under the terms of the GNU Lesser General Public
   License as published by the Free Software Foundation; either
   version 2.1 of the License, or (at your option) any later version.

   This program is distributed in the hope that it will be useful, but
   WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
   Lesser General Public License for more details.

   You should have received a copy of the GNU Lesser General Public
   License along with this program; if not, write to the Free
(Continue reading)

Permalink | Reply | 0 comments |

Gmane