From: Ian Roxborough <irox@redhat.com>
To: leonp@plris.com
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: My attempt to change the linker fails
Date: Wed, 28 Mar 2001 16:37:00 -0000 [thread overview]
Message-ID: <3AC2839A.EBF799B8@redhat.com> (raw)
In-Reply-To: <5.0.2.1.0.20010328103937.00a7bea0@plris.com>
I beleave that this is bug, if I remember correctly this
is fixed in the up comming 5.0 release (sooooooooooon ok).
If you can't wait (I can't give you a date for the 5.0
release) until then, you could edit the file
<your-install-dir>/share/gui/toolchain.tcl to use
gcc166 instead of gcc, this might be a better since
you won't have to change the compiler and linker
every time you create a build target.
Ian.
leonp@plris.com wrote:
>
> Hello,
> I use the SN for cross development (this time under Win2K without
> CygWin) and have the following question:
> When I open the build target settings editing dialog (which has
> the Source, Library, Build, Link tabs), each of its tabs has 3 items to the
> right. The last is called "Tool chain" and has 3 GNUpro options. I am able
> to substitute compiler name to the compiler I need (in my case this is
> gcc166) by editing build rule "executable" item. This leads to the CC
> variable in snMakefile to be set to my value. But my attemp to do the same
> in "Link Rools -> Linker" fails. SN constantly returns
> ..-gnu-ar definition in this text box, while in snMakefile remains
> definition of LINKER=...gnu-ar.
>
> Thanks ahead.
>
> Leon Pollak
> leonp@plris.com
prev parent reply other threads:[~2001-03-28 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 3:41 leonp
2001-03-28 16:37 ` Ian Roxborough [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AC2839A.EBF799B8@redhat.com \
--to=irox@redhat.com \
--cc=leonp@plris.com \
--cc=sourcenav@sourceware.cygnus.com \
/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.
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).