From: Ryan Yeske <rcyeske@gmail.com>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: 22.0.98 build problem
Date: Wed, 25 Apr 2007 21:16:06 -0700 (PDT) [thread overview]
Message-ID: <20070426041606.25742142E4@owie.localdomain> (raw)
In-Reply-To: <E1HgNUc-0003pu-Ou@fencepost.gnu.org>
I think the problem is due to the absence of -nostdlib in the command
to link. So I think the bug is in the conversion of Makefile.in
into Makefile. Can you investigate what happens and how it comes about
that -nostdlib is missing?
That is true, if I add -nostdlib to the Makefile by hand, I can build.
It is not very clear to me what needs to be changed to add -nostdlib
for this platform. What is the condition?
FWIW, There are two places in src/Makefile.in that I can find -nostdlib
/* Versions of GCC >= 2.0 put their library, libgcc.a, in obscure
places that are difficult to figure out at make time. Fortunately,
these same versions allow you to pass arbitrary flags on to the
linker, so there is no reason not to use it as a linker.
Well, it is not quite perfect. The "-nostdlib" keeps GCC from
searching for libraries in its internal directories, so we have to
ask GCC explicitly where to find libgcc.a. */
#ifndef LINKER
#define LINKER $(CC) -nostdlib
#endif
and
#ifdef ORDINARY_LINK
LD = $(CC)
#else
#ifdef COFF_ENCAPSULATE
LD=$(CC) -nostdlib
#else /* not ORDINARY_LINK */
#ifdef LINKER
LD=LINKER
#else /* not LINKER */
LD=ld
#endif /* not LINKER */
#endif /* not COFF_ENCAPSULATE */
#endif /* not ORDINARY_LINK */
next prev parent reply other threads:[~2007-04-26 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 19:19 22.0.98 build problem Ryan Yeske
2007-04-23 19:40 ` Alfred M. Szmidt
2007-04-23 21:14 ` Ryan Yeske
2007-04-24 16:03 ` Richard Stallman
2007-04-26 4:16 ` Ryan Yeske [this message]
2007-04-26 7:27 ` Glenn Morris
2007-04-26 9:01 ` Ryan Yeske
2007-04-28 4:41 ` Glenn Morris
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=20070426041606.25742142E4@owie.localdomain \
--to=rcyeske@gmail.com \
--cc=emacs-devel@gnu.org \
--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 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).