From: MALET JL <malet.jean-luc@laposte.net>
To: Chris Lingard <chris@ukpost.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux 2.6.3] [gcc 3.3.3] compile errors
Date: Tue, 24 Feb 2004 09:42:58 +0100 [thread overview]
Message-ID: <403B0E92.60903@laposte.net> (raw)
In-Reply-To: <200402231658.53516.chris@ukpost.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Chris Lingard a écrit :
>On Monday 23 February 2004 4:31 pm, MALET JL wrote:
>
>
>
>>copy from /usr/src/linux/include/asm to /usr/include/asm
>>copy from /usr/src/linux/include/asm-generic to /usr/include/asm-generic
>>copy from /usr/src/linux/include/linux to /usr/include/linux
>>
>>is this wrong ? I've done this all the time (since 2.4.2 kernel) without
>>problem..... if i'm wrong please correct my behaviour
>>
>>
>
>You should use the kernel headers to build glibc; and sanitised headers
>such as RedHat's or http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
>to build the rest of the system. Suggest you follow www.linuxfromscratch.org
>for further details.
>
>Chris
>
>
O_O! question what is the purpose of having two set of headers? do you
think this is good work to provide a unsable set of headers with a
software? why not include the RedHat's one then......
[-- Attachment #2: Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2004-02-24 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 20:31 [linux 2.6.3] [gcc 3.3.3] compile errors mjl
2004-02-23 15:42 ` Randy.Dunlap
2004-02-23 16:31 ` MALET JL
2004-02-23 16:58 ` Chris Lingard
2004-02-24 8:42 ` MALET JL [this message]
2004-02-24 10:46 ` [linux 2.6.3] [gcc 3.3.3] compile errors. Now OT Chris Lingard
2004-02-23 20:52 ` [linux 2.6.3] [gcc 3.3.3] compile errors Martin Schlemmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403B0E92.60903@laposte.net \
--to=malet.jean-luc@laposte.net \
--cc=chris@ukpost.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox