From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: Re: nap() name space clash
Date: Wed, 05 Feb 2020 03:03:33 +0100 [thread overview]
Message-ID: <3741324.LZzoxjWToW@omega> (raw)
In-Reply-To: <alpine.UW2.2.11.2002040845260.5034@server01.int.multitalents.net>
Hi Tim,
> > > I discoverd a name space clash with nap()
> >
> > In which .h file is this function declared on UnixWare?
>
> unistd.h
Can you find out whether defining some preprocessor symbol will make
the declaration disappear? You need to peek into the .h file, make a
guess, and then process the file
#include <unistd.h>
int nap;
with "gcc -E ... | grep nap".
> > > How do I find out if I have filled out copyright assignment papers
> > > for the gnulib project?
>
> OK, I wil need to do that for gnulib. I have been siting on a bunch of
> patches way too long.
> Hmm, not all that ewasy to find the right assignent papers and who to send
> them to.
The right form should be doc/Copyright/request-assign.future (in the gnulib
repository).
Bruno
next prev parent reply other threads:[~2020-02-05 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 5:34 nap() name space clash Tim Rice
2020-02-04 10:47 ` Bruno Haible
2020-02-04 17:02 ` Tim Rice
2020-02-05 2:03 ` Bruno Haible [this message]
2020-02-06 23:37 ` Tim Rice
2020-09-24 5:33 ` Tim Rice
2020-10-11 18:55 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3741324.LZzoxjWToW@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).