From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] libxl: build fix
Date: Wed, 14 Apr 2010 09:19:46 +0200 [thread overview]
Message-ID: <201004140919.46969.Christoph.Egger@amd.com> (raw)
In-Reply-To: <19396.34784.712035.704699@mariner.uk.xensource.com>
On Tuesday 13 April 2010 17:04:00 Ian Jackson wrote:
> Christoph Egger writes ("Re: [Xen-devel] [PATCH] libxl: build fix"):
> > On NetBSD, the SIG* defines are in <sys/signal.h> which is just
> > included by <signal.h>
> > On NetBSD, both works.
>
> The correct way to discover what the right #include is is not to go on
> a wild goose chase through headers. It is to read appropriate
> documentation, such as SuSv3:
> http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html
> Every function or symbol that's in SuS has next to its description a
> statement of what header file(s) are needed.
Yes, you are right. It's my fault. It should have read the manpage. It states
this clearly, too.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-04-14 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 10:16 [PATCH] libxl: build fix Christoph Egger
2010-04-13 11:21 ` Ian Jackson
2010-04-13 11:49 ` Christoph Egger
2010-04-13 15:04 ` Ian Jackson
2010-04-14 7:19 ` Christoph Egger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-16 15:51 Christoph Egger
2012-05-17 11:41 ` Roger Pau Monne
2012-05-17 11:44 ` Ian Campbell
2012-05-17 13:47 ` Ian Campbell
2011-01-11 14:54 Christoph Egger
2011-01-11 18:44 ` Ian Jackson
2009-12-01 14:40 Christoph Egger
2009-12-04 15:52 ` Ian Jackson
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=201004140919.46969.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.