delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-workers-bounces using -f |
Date: | Sun, 1 May 2011 13:15:41 -0400 |
Message-Id: | <201105011715.p41HFfTe002301@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <831v0i5ps4.fsf@gnu.org> (message from Eli Zaretskii on Sun, 01 |
May 2011 19:50:03 +0300) | |
Subject: | Re: djgpp*.djl |
References: | <4DBD4955 DOT 3060104 AT iki DOT fi> <831v0i5ps4 DOT fsf AT gnu DOT org> |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> I'm ashamed to admit that I forgot why we have this file. I know that > it's a linker script, but why do we have our own in libc? Linker scripts come from one of three places: 1. Binutils - LD has a default built-in. 2. libc - djlsr, libgloss, glibc, etc. 3. project - you can provide a local script in your build. At the time, djgpp was changing much faster than binutils or gcc, so we needed to be able to ensure we had the correct and latest linker script to go with our library.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |