unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: CVS emacs crashes right after startup
Date: Mon, 19 Jan 2004 23:01:33 +0200	[thread overview]
Message-ID: <9003-Mon19Jan2004230133+0200-eliz@elta.co.il> (raw)
In-Reply-To: <q5gd69gjfpg.fsf@lucent.com> (message from Klaus Zeitler on 19 Jan 2004 13:16:59 +0100)

> From: Klaus Zeitler <kzeitler@lucent.com>
> Date: 19 Jan 2004 13:16:59 +0100
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@elta.co.il> writes:
>     Eli> 
>     Eli> Can you force GCC 3.2.2 to invoke the Solaris linker, and see if that
>     Eli> helps?
> 
> if I only knew how. According to gccint info I think it should be possible
> 
> ---snip ---
>    The program `collect2' is installed as `ld' in the directory where
> the passes of the compiler are installed.  When `collect2' needs to
> find the _real_ `ld', it tries the following file names:
> 
>    * `real-ld' in the directories listed in the compiler's search
>      directories.
> 
>    * `real-ld' in the directories listed in the environment variable
>      `PATH'.
> 
>    * The file specified in the `REAL_LD_FILE_NAME' configuration macro,
>      if specified.
> 
>    * `ld' in the compiler's search directories, except that `collect2'
>      will not execute itself recursively.
> 
>    * `ld' in `PATH'.
> 
>    "The compiler's search directories" means all the directories where
> `gcc' searches for passes of the compiler.  This includes directories
> that you specify with `-B'.
> --- snip ---
> I've tried a link of real-ld to SUN ld and made sure that this link and also
> SUN ld are found first in my PATH, but gcc 3.3.2 always calls GNU ld.
> Do you know how I can force the use of a specific linker? If not I guess
> I have to ask in gnu.help.gcc.

Please wait for a while, perhaps someone here will know (I've cc'ed
emacs-devel, in the hope that more people will read this).  If not,
asking on the GCC lists is a good idea.

Thanks for working on this.

       reply	other threads:[~2004-01-19 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <q5g3carew8j.fsf@lucent.com>
     [not found] ` <q5goeteekqq.fsf@lucent.com>
     [not found]   ` <uvfnm7el3.fsf@elta.co.il>
     [not found]     ` <q5gr7y5xq7w.fsf@lucent.com>
     [not found]       ` <q5gd69gjfpg.fsf@lucent.com>
2004-01-19 21:01         ` Eli Zaretskii [this message]
2004-02-02 12:03           ` CVS emacs crashes right after startup Klaus Zeitler
2004-02-02 18:49             ` Eli Zaretskii
2004-02-03 14:35             ` Richard Stallman
2004-02-04 10:19               ` Klaus Zeitler
2004-02-04 11:14                 ` Eli Zaretskii
2004-02-05  9:27                   ` Klaus Zeitler
2004-02-04 17:47                 ` Stefan Monnier
2004-02-04 18:36                   ` Eli Zaretskii
2004-02-18  5:55                 ` Eli Zaretskii

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=9003-Mon19Jan2004230133+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@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).