unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc: Frank Schmitt <ich@frank-schmitt.net>, emacs-devel@gnu.org
Subject: Re: RFC: Support for FreeBSD/amd64
Date: Sat, 29 Oct 2005 01:01:11 +0300	[thread overview]
Message-ID: <20051028220111.GA20317@flame.pc> (raw)
In-Reply-To: <E1EVYf4-0006vu-P1@fencepost.gnu.org>

On 2005-10-28 14:09, "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.

Something like this perhaps?

http://people.freebsd.org/~keramida/emacs/22/freebsd-amd64+libgcc.patch

I took the liberty of adding a comment to the __FreeBSD__ #ifdef for the
location of the 64-bit libraries.

  reply	other threads:[~2005-10-28 22:01 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20051028220111.GA20317@flame.pc \
    --to=keramida@ceid.upatras.gr \
    --cc=emacs-devel@gnu.org \
    --cc=ich@frank-schmitt.net \
    /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.savannah.gnu.org/cgit/emacs.git

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