From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc: emacs-devel@gnu.org, rms@gnu.org, ich@frank-schmitt.net
Subject: Re: RFC: Support for FreeBSD/amd64
Date: Sat, 29 Oct 2005 21:35:45 +0300 [thread overview]
Message-ID: <20051029183545.GA7351@flame.pc> (raw)
In-Reply-To: <u8xwcskjt.fsf@gnu.org>
On 2005-10-29 12:07, Eli Zaretskii <eliz@gnu.org> wrote:
>Richard M. Stallman <rms@gnu.org> wrote:
>>> Yes, and they both are almost certainly needed. The reason is that
>>> some functions in libgcc.a call functions from libc.a, and some
>>> libc.a functions need functions from libgcc.a. Since most versions
>>> of ld are one-pass linkers, you need to mention -lgcc twice, or else
>>> risk getting unresolved externals.
>>
>> Someone should add a comment above that line
>> to explain this.
>
> I don't object to such a comment, of course, but I thought this
> was common knowledge. E.g., anyone who has ever invoked GCC
> with the -v option to build a C program already knows that GCC
> mentions -lgcc twice on the linker's command line.
The original suggestion for a comment was triggered from my own
comment that the duplicate -lgcc was probably intentional, but I
didn't know the reason. Now I know the answer, but it may still
be worth to document it near the relevant part of the source ;-)
- Giorgos
next prev parent reply other threads:[~2005-10-29 18:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 23:52 RFC: Support for FreeBSD/amd64 Giorgos Keramidas
2005-10-27 3:58 ` Richard M. Stallman
2005-10-27 6:50 ` Frank Schmitt
2005-10-27 11:50 ` Giorgos Keramidas
2005-10-27 19:08 ` Eli Zaretskii
2005-10-27 20:13 ` Giorgos Keramidas
2005-10-27 20:56 ` Frank Schmitt
2005-10-28 18:09 ` Richard M. Stallman
2005-10-28 22:01 ` Giorgos Keramidas
2005-10-29 5:12 ` Richard M. Stallman
2005-10-29 14:47 ` Giorgos Keramidas
2005-10-30 3:36 ` Richard M. Stallman
2005-10-29 10:07 ` Eli Zaretskii
2005-10-29 18:35 ` Giorgos Keramidas [this message]
2005-10-29 20:33 ` Richard M. Stallman
2005-10-27 12:27 ` Dryice Liu
2005-10-27 14:57 ` Giorgos Keramidas
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=20051029183545.GA7351@flame.pc \
--to=keramida@ceid.upatras.gr \
--cc=emacs-devel@gnu.org \
--cc=ich@frank-schmitt.net \
--cc=rms@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.