public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* am33_2.0-*-linux* -- why no t-slibgcc-elf-ver ?
@ 2003-10-09 16:07 Nathanael Nerode
  2003-10-09 23:34 ` Alexandre Oliva
  0 siblings, 1 reply; 2+ messages in thread
From: Nathanael Nerode @ 2003-10-09 16:07 UTC (permalink / raw)
  To: gcc

This is the only linux target (except the remaining linux-aout target)
 which doesn't include the t-slibgcc-elf-ver fragment.

Is there a reason for this or is it just an accident?

-- 
Nathanael Nerode  <neroden at gcc.gnu.org>
http://home.twcny.rr.com/nerode/neroden/fdl.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: am33_2.0-*-linux* -- why no t-slibgcc-elf-ver ?
  2003-10-09 16:07 am33_2.0-*-linux* -- why no t-slibgcc-elf-ver ? Nathanael Nerode
@ 2003-10-09 23:34 ` Alexandre Oliva
  0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Oliva @ 2003-10-09 23:34 UTC (permalink / raw)
  To: Nathanael Nerode; +Cc: gcc

On Oct  9, 2003, neroden@twcny.rr.com (Nathanael Nerode) wrote:

> This is the only linux target (except the remaining linux-aout target)
>  which doesn't include the t-slibgcc-elf-ver fragment.

> Is there a reason for this or is it just an accident?

Oversight, most definitely.  I believe the original am33_2.0-linux-gnu
port pre-dates t-slibgcc-elf-ver, even though it was contributed *far*
later.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-10-09 21:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-10-09 16:07 am33_2.0-*-linux* -- why no t-slibgcc-elf-ver ? Nathanael Nerode
2003-10-09 23:34 ` Alexandre Oliva

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).