caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Keyan <ml@pulsschlag.net>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Bug in libunix.a + Patch
Date: Fri, 20 Jul 2012 19:13:31 +0200	[thread overview]
Message-ID: <2F636BDB-7F60-44C4-A9E4-B0D7E2A6BE45@pulsschlag.net> (raw)
In-Reply-To: <5009880D.8000005@inria.fr>

Hi,

I will post it on the bug tracker too. My setting is:

Mac OS X 10.7.4
gcc version: i686-apple-darwin11-llvm-gcc-4.2
ocaml 3.12.1
Xcode 4.3.3 (4E3002)

I don't develop in Xcode, but use makefiles instead. Homebrew was used to install ocaml.

The error only occurs when linking to a dynamic lib, not when I link against an executable (main loop in c).

Best,
Keyan


On 20 Jul 2012, at 18:32, Xavier Leroy wrote:

> On 07/20/2012 04:45 PM, Keyan wrote:
> 
>> _envrion was not found, when linking libunix.a to a library on Mac
> OS X:
>> 
>> Undefined symbols for architecture x86_64:
>>  "_environ", referenced from:
>>      _unix_execvpe in libunix.a(execvp.o)
>>      _unix_environment in libunix.a(envir.o)
> 
> At the risk of sounding like a broken record, could you please file a
> report on our bug tracker:
> http://caml.inria.fr/mantis/
> It's the best way to ensure that the issue will not slip past our radar.
> 
> Also, please tell us which versions of MacOS X and of Xcode you're using.
> 
> Because this sounds very much like a bug in the C library or in the
> linker: the "environ" variable is standardized as part of POSIX and
> derived standard like the Single Unix Specification, and MacOS X has
> been very very good so far at following POSIX standards.
> 
> - Xavier Leroy


  reply	other threads:[~2012-07-20 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 14:45 Keyan
2012-07-20 16:32 ` Xavier Leroy
2012-07-20 17:13   ` Keyan [this message]
2012-07-20 18:49     ` Benedikt Meurer

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=2F636BDB-7F60-44C4-A9E4-B0D7E2A6BE45@pulsschlag.net \
    --to=ml@pulsschlag.net \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    /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).