unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: patch to build guile CVS on Mac OS X
Date: Wed, 07 Jan 2004 08:00:28 +1000	[thread overview]
Message-ID: <87vfno91qb.fsf@zip.com.au> (raw)
In-Reply-To: <20040106101709.GA27012@Richard-Todds-Computer.local> (Richard Todd's message of "Tue, 6 Jan 2004 04:17:10 -0600")

Richard Todd <richardt@vzavenue.net> writes:
>
> +#if defined(__APPLE__) && defined(__DYNAMIC__)
> +#include<crt_externs.h>
> +static char ** environ;
> +#else
>  extern char ** environ;
> +#endif 
>  
>  #ifdef HAVE_GRP_H
>  #include <grp.h>
> @@ -1735,6 +1740,10 @@
>  void 
>  scm_init_posix ()
>  {
> +#if defined(__APPLE__) && defined(__DYNAMIC__)
> +  environ = *_NSGetEnviron();
> +#endif
> +

That's really weird.  I'd rather not do that if it can be avoided.

Surely they can't expect every library that accesses environ to get a
system-specific change?

Does it work to take the declaration of environ from <stdlib.h>
instead of giving an explicit "extern"?  The autoconf way is normally
to let the headers do the job where possible.


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


  parent reply	other threads:[~2004-01-06 22:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 10:17 patch to build guile CVS on Mac OS X Richard Todd
2004-01-06 21:53 ` Kevin Ryde
2004-01-06 22:00 ` Kevin Ryde [this message]
2004-01-06 23:16   ` Richard Todd
2004-01-06 23:30     ` Kevin Ryde
2004-01-07  0:06       ` Richard Todd
2004-01-07  0:37         ` Kevin Ryde
2004-01-06 23:02 ` Kevin Ryde
2004-01-06 23:30   ` Richard Todd
2004-01-06 23:44     ` Kevin Ryde

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vfno91qb.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=bug-guile@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).