mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: [compatability] sys/cdefs.h not shipped
Date: Wed, 7 Sep 2011 23:02:44 -0700	[thread overview]
Message-ID: <20110907230244.0cd92284.idunham@lavabit.com> (raw)
In-Reply-To: <20110907201105.GL132@brightrain.aerifal.cx>

On Wed, 7 Sep 2011 16:11:05 -0400
Rich Felker <dalias@aerifal.cx> wrote:

> On Tue, Sep 06, 2011 at 11:48:13PM -0700, Isaac Dunham wrote:
> > sys/cdefs.h is required by TI-RPC (an ipv6 compatible derivative of
> > the 'sun-rpc' code in gnu libc) and by libbsd; there are certainly

> Could you elaborate on what's needed from this file? It's definitely a
> bug for any program to be using the stuff in cdefs.h, which is pretty
> much all double-underscore-prefixed macros for internal use by glibc
> to facilitate compiling in pre-ANSI C compilers, which is almost
> certainly not going to work anyway. Is TI-RPC working on other
> non-GNU/Linux systems, which probably don't have this header?
> 
> Rich
> 
Looks like the issue's mostly __BEGIN_DECLS & __END_DECLS, 
which glibc does thus:
#ifdef  __cplusplus
# define __BEGIN_DECLS  extern "C" {
# define __END_DECLS    }
#else
# define __BEGIN_DECLS
# define __END_DECLS
#endif
(Also, sys/cdefs.h exports c90 functions in namespace std, and does other stuff to let headers work with both C & C++).
Besides that, configure has no idea how to handle musl or the machine name, and the chroot I'm using needs fixing...
-- 
Isaac Dunham <idunham@lavabit.com>



      reply	other threads:[~2011-09-08  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  6:48 Isaac Dunham
2011-09-07 20:11 ` Rich Felker
2011-09-08  6:02   ` Isaac Dunham [this message]

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=20110907230244.0cd92284.idunham@lavabit.com \
    --to=idunham@lavabit.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).