public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egall at gwmail dot gwu.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63758] liblto_plugin.so has undefined reference to _environ on OSX
Date: Thu, 03 Sep 2015 18:08:00 -0000 [thread overview]
Message-ID: <bug-63758-4-2q6yyUz7zH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63758-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63758
Eric Gallager <egall at gwmail dot gwu.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egall at gwmail dot gwu.edu
--- Comment #7 from Eric Gallager <egall at gwmail dot gwu.edu> ---
(In reply to Iain Sandoe from comment #4)
> Created attachment 34311 [details]
> Updated patch to catch another use.
>
> I'm taking this bug, if that's OK
> I'd like to post the revised patch to @patches
> ... but Roland can you confirm that's OK with you?
Re: the location of the "environ.h" added: could you put it in the include/
directory instead of in the libiberty/ directory, so that other directories in
the tree can use it more easily? libgcj, for instance, could use it, too, to
solve bug 38812, apparently...
next prev parent reply other threads:[~2015-09-03 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 0:14 [Bug other/63758] New: " roland at gnu dot org
2014-11-06 0:17 ` [Bug other/63758] " roland at gnu dot org
2014-11-06 9:44 ` rguenth at gcc dot gnu.org
2014-11-27 23:34 ` iains at gcc dot gnu.org
2014-12-22 13:09 ` iains at gcc dot gnu.org
2015-09-03 12:42 ` nickc at redhat dot com
2015-09-03 13:44 ` iains at gcc dot gnu.org
2015-09-03 18:08 ` egall at gwmail dot gwu.edu [this message]
2015-09-07 15:27 ` iains at gcc dot gnu.org
2015-10-18 10:34 ` iains at gcc dot gnu.org
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=bug-63758-4-2q6yyUz7zH@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).