From: David Woodhouse <dwmw2@infradead.org>
To: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
Cc: schilling@fokus.fraunhofer.de, linux-kernel@vger.kernel.org,
david@lang.hm
Subject: Re: Linux Kernel include files
Date: Mon, 25 Jun 2007 16:27:57 +0100 [thread overview]
Message-ID: <1182785277.12109.121.camel@pmac.infradead.org> (raw)
In-Reply-To: <467fdc75.0ficjl92unPDO1uk%Joerg.Schilling@fokus.fraunhofer.de>
On Mon, 2007-06-25 at 17:17 +0200, Joerg Schilling wrote:
> David Woodhouse <dwmw2@infradead.org> wrote:
> > On Fri, 2007-06-22 at 01:38 +0200, Joerg Schilling wrote:
> A kernel include file that defines an interface to a user space program
> should be self containing (that means that all includes for all non-standard
> types should be done inside these include files). Whether or not C-99
> types are used or not is less important than to use type definitions written
> in clean C so compilers other than gcc may use them.
Yes. In general we try to achieve this. Most header files should include
<asm/types.h>, which tends to define the types we use in terms which
should work in any compiler.
> > Can you be more specific about why this is a problem? Don't
> > we mostly define those crappy types using arch-specific knowledge, as
> > 'int', 'long', etc?
>
> I recommend you to install Sun Studio and to try to compile star or cdrtools
> using Sun Studio by calling "make CCOM_suncc".
>
> ftp://ftp.berlios.de/pub/star/alpha/
> ftp://ftp.berlios.de/pub/cdrecord/alpha/
>
> You may need to hand edit the file incs/<arch-dir>/{xconfig.h!rules.conf}
>
> in order to enable the auto-disabled features.
>
> In any case, self reading the error messages from Sun Studio helps more than
> trying to discuss it.
I have no interest in doing this for myself, and I suspect that if I
tried it I'd find that Sun Studio doesn't exist for Linux/PowerPC
anyway. Please just show the error messages.
--
dwmw2
next prev parent reply other threads:[~2007-06-25 15:28 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 22:32 Linux Kernel include files Joerg Schilling
2007-06-21 23:25 ` david
2007-06-21 23:38 ` Joerg Schilling
2007-06-22 3:38 ` David Woodhouse
2007-06-22 5:18 ` H. Peter Anvin
2007-06-22 15:00 ` Adrian Bunk
2007-06-26 15:26 ` H. Peter Anvin
2007-06-27 1:32 ` Kyle Moffett
2007-06-27 15:40 ` Adrian Bunk
2007-06-27 15:52 ` Joerg Schilling
2007-06-27 15:59 ` Robert P. J. Day
2007-06-27 17:32 ` Userspace compiler support of "long long" Adrian Bunk
2007-06-27 22:30 ` Kyle Moffett
2007-06-27 22:57 ` Randy Dunlap
2007-06-27 23:16 ` Randy Dunlap
2007-06-28 2:12 ` Geert Uytterhoeven
2007-06-28 6:50 ` Jan Engelhardt
2007-06-28 11:34 ` Geert Uytterhoeven
2007-06-28 11:36 ` David Woodhouse
2007-06-28 12:20 ` Kyle Moffett
2007-06-28 3:06 ` Kyle McMartin
2007-06-28 0:30 ` Andi Kleen
2007-06-28 11:42 ` Kyle Moffett
2007-06-28 3:57 ` Matthew Wilcox
2007-06-28 11:53 ` Kyle Moffett
2007-06-28 12:08 ` Jakub Jelinek
2007-06-28 12:18 ` Kyle Moffett
2007-06-28 4:03 ` H. Peter Anvin
2007-06-28 10:26 ` Harald Arnesen
2007-06-28 10:44 ` Joerg Schilling
2007-06-28 12:11 ` Kyle Moffett
2007-06-28 15:31 ` Mark Brown
2007-06-28 4:02 ` Linux Kernel include files H. Peter Anvin
2007-06-25 15:17 ` Joerg Schilling
2007-06-25 15:27 ` David Woodhouse [this message]
2007-06-25 18:04 ` Harald Arnesen
2007-06-25 20:26 ` Joerg Schilling
2007-06-25 20:32 ` David Woodhouse
2007-06-25 21:43 ` Harald Arnesen
2007-06-25 21:48 ` Harald Arnesen
2007-06-25 21:49 ` Joerg Schilling
2007-06-25 22:30 ` Harald Arnesen
2007-06-25 22:42 ` Joerg Schilling
2007-06-21 23:59 ` Arnd Bergmann
2007-06-25 15:06 ` Joerg Schilling
2007-06-25 16:00 ` david
2007-06-25 14:48 ` Joerg Schilling
2007-06-21 23:47 ` Arjan van de Ven
2007-06-25 14:53 ` Joerg Schilling
2007-06-25 15:26 ` Arjan van de Ven
2007-06-25 15:27 ` Robert P. J. Day
2007-06-25 20:18 ` Sam Ravnborg
2007-06-27 13:45 Joerg Schilling
2007-06-27 22:16 ` H. Peter Anvin
2007-06-27 13:58 Joerg Schilling
2007-06-27 16:40 ` Adrian Bunk
2007-06-27 16:41 ` Joerg Schilling
2007-06-27 18:50 ` Arjan van de Ven
2007-06-27 17:18 ` Sam Ravnborg
2007-06-28 10:47 ` Joerg Schilling
2007-06-28 13:49 ` Jan Engelhardt
2007-06-29 12:59 ` David Woodhouse
2007-06-27 14:00 Joerg Schilling
2007-06-27 16:04 ` David Woodhouse
2007-06-28 10:27 ` Joerg Schilling
2007-06-28 10:37 ` David Woodhouse
2007-06-28 10:39 ` Joerg Schilling
2007-06-28 10:57 ` Jan-Benedict Glaw
2007-06-28 16:15 ` Jan Engelhardt
[not found] <8AGnE-33a-15@gated-at.bofh.it>
[not found] ` <8AISu-6Qn-31@gated-at.bofh.it>
[not found] ` <8AISu-6Qn-29@gated-at.bofh.it>
[not found] ` <8AKUp-1wx-41@gated-at.bofh.it>
2007-06-27 22:35 ` Bodo Eggert
2007-06-27 23:07 ` Arjan van de Ven
[not found] <8AGnE-33a-13@gated-at.bofh.it>
[not found] ` <8AIfO-63r-29@gated-at.bofh.it>
[not found] ` <8AZJA-7BV-3@gated-at.bofh.it>
[not found] ` <8AZJA-7BV-1@gated-at.bofh.it>
[not found] ` <8AZJQ-7BV-15@gated-at.bofh.it>
[not found] ` <8AZTo-7OT-3@gated-at.bofh.it>
[not found] ` <8B4T2-7py-37@gated-at.bofh.it>
2007-07-01 9:47 ` Bodo Eggert
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=1182785277.12109.121.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=schilling@fokus.fraunhofer.de \
/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;
as well as URLs for NNTP newsgroup(s).