From: Richard Stallman <rms@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: compiling with non-gcc
Date: Tue, 24 Sep 2002 13:14:00 -0400 [thread overview]
Message-ID: <E17ttG4-0001Ab-00@fencepost.gnu.org> (raw)
In-Reply-To: <20020923220423.67e25282.occitan@esperanto.org> (message from Daniel Pfeiffer on Mon, 23 Sep 2002 22:04:23 +0200)
> It should not be trying to use -lgcc if it is not compiling with GCC.
That's what I figured! I'm attaching the produced files.
I'm not going to spend time on the Intel compiler myself,
but maybe someone else will decide to.
prev parent reply other threads:[~2002-09-24 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 20:10 compiling with non-gcc Daniel Pfeiffer
2002-09-23 15:59 ` Richard Stallman
2002-09-23 20:04 ` Daniel Pfeiffer
2002-09-24 17:14 ` Richard Stallman [this message]
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=E17ttG4-0001Ab-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@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).