Re: Porting gcc to a nonstandard platform requires to call external program after linking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Cosimo Caproni <cosimocaproni@xxxxxx>
Subject: Re: Porting gcc to a nonstandard platform requires to call external program after linking
From: Ian Lance Taylor <iant@xxxxxxxxxx>
Date: Fri, 15 Mar 2013 06:27:18 -0700
Cc: "gcc-help@xxxxxxxxxxx" <gcc-help@xxxxxxxxxxx>
Comment: DKIM? See http://www.dkim.org
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
In-reply-to: <E1DEAA23-01D6-4A7C-8A45-B86E10EC84E8@me.com>

On Fri, Mar 15, 2013 at 3:14 AM, Cosimo Caproni <cosimocaproni@xxxxxx> wrote:

> I am currently working in porting gcc to a non standard platform
> which requires to call a program after having linked the program in
> order to make it executable. Where can I add such call?

In LINK_COMMAND_SPEC.

Ian

References:
- Porting gcc to a nonstandard platform requires to call external program after linking
  - From: Cosimo Caproni

Prev by Date: Re: Automatic accessor function inlining
Next by Date: Re: Porting gcc to a nonstandard platform requires to call external program after linking
Previous by thread: Porting gcc to a nonstandard platform requires to call external program after linking
Next by thread: Re: Porting gcc to a nonstandard platform requires to call external program after linking
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux