Re: Obsoleting unmaintained targets

Re: Obsoleting unmaintained targets

[DANIEL NORMAN HARRIS]

Dear Jim;
I don't know what this message is all about. I could play the Emperor's new
Clothes with you, but so far as I can tell you are on about accessing
features in some sort of code you mean to change. I am interested in getting
a FORTRAN that runs in Win95. You can probably tell me what wonderful things
your site does as well when there is a download link for that module. I am
not averse to having new knowledge. I had initially to force myself to look
at Linux and have install diskettes but am not brave enough to put it into a
computer as yet. Maybe one day I will have the guts, but what I have is what
I use, not what I meddle with. GNU is compared to Linux, how and in what way
is not certain to me. Why not fill me in on what fabulous wonders are
enabled by the GNU system?
-----Original Message-----
From: Jim Wilson <wilson@specifixinc.com>
To: gcc-announce@gcc.gnu.org <gcc-announce@gcc.gnu.org>
Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Date: Wednesday, December 03, 2003 10:31 AM
Subject: Obsoleting unmaintained targets


>In the GCC 3.4 release (still some time in the future), the GCC
>developers are obsoleting a number of old unmaintained targets.
>Obsoleting these old systems allows the development team to focus its
>limited resources to support those systems that are used by more people.
>
>These targets can still be configured by using the --enable-obsolete
>option.  If no one steps forward to maintain these targets, they will be
>deleted in a future gcc release.
>
>Below, please find the complete list, in the form of GNU target
>triplets.  This has been extensively revised from the list that was
>originally posted in March.
>
>If you feel strongly that support for one of these targets should not be
>removed, please contact us by email to gcc@gcc.gnu.org.  Traditionally,
>GCC has been more receptive to requests that a particular target not be
>removed if a volunteer is available to maintain that target, so if
>you're interested in volunteering you should state that explicitly.
>Also, "there are 1000 of us using this machine heavily all day long and
>we were planning to upgrade to GCC 3.4" is probably more likely to sway
>the development team than "I think there is still one of those in my
>closet." :-)
>
>All targets for these architectures have been obsoleted:
> d30v-*
> dsp16xx-*
> i370-*
> i960-*
>
>Individual targets that have been obsoleted:
> i?86-moss-msdos
> i?86-*-moss*
> i?86-ncr-sysv4*
> i?86-*-netware
> i?86-*-freebsd2*
> i?86-*-freebsd*aout*
> i?86-*-linux*aout*
> i?86-*-linux*libc1*
> # This does not affect Interix3 support which remains.
> i?86-*-interix
> i?86-*-mach*
> i?86-*-udk*
> i?86-*-sysv[123]*
> i386-*-vsta
>
> m68k-hp-hpux*
> m68000-hp-hpux*
> m68k-*-sysv4*
>
> # This is only the a.out netbsd targets, the elf netbsd targets
> # remain.
> m68k*-*-netbsd*
>
> # This is only the default target, which is no longer useful.
> # The *BSD, Ultrix, and Sysv targets remain.
> vax-*-*
>--
>Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
>

Re: Obsoleting unmaintained targets

[Jim Wilson]

DANIEL NORMAN HARRIS wrote:
> features in some sort of code you mean to change. I am interested in getting
> a FORTRAN that runs in Win95.

See
	http://www.cygwin.com
	http://www.mingw.org
for two different projects that support gcc running on MS Windows.  The 
first one provides a large POSIX (Unix like) environment.  The second 
one provides a minimal environment, relying more on MS libraries.  They 
both provide binaries for downloading.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Re: Obsoleting unmaintained targets

[Phil Edwards]

On Thu, Dec 04, 2003 at 07:07:19AM +0800, Emmanuel R. Matuco wrote:
> Really much thanks for sharing me this development. 
> I never thought, a small-time student of programming like me would be
> given equal attention. Until now I haven't been successful in
> downloading the gcc c compiler. Am still lost in navigating my way on
> how to download it.

You go to the gcc.gnu.org website and look on the left, under
the "Download" heading.

But you don't click on anything yet.  First you go up a little
bit, to the "Installation" heading, and read that first.

-- 
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
    - Brian W. Kernighan

RE: Obsoleting unmaintained targets

[Emmanuel R. Matuco]

Really much thanks for sharing me this development. 
I never thought, a small-time student of programming like me would be
given equal attention. Until now I haven't been successful in
downloading the gcc c compiler. Am still lost in navigating my way on
how to download it.

Really much thanks for your care in sharing this email.
Take care.


-----Original Message-----
From: gcc-announce-owner@gcc.gnu.org
[mailto:gcc-announce-owner@gcc.gnu.org] On Behalf Of Jim Wilson
Sent: Wednesday, December 03, 2003 7:19 AM
To: gcc-announce@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: Obsoleting unmaintained targets

In the GCC 3.4 release (still some time in the future), the GCC 
developers are obsoleting a number of old unmaintained targets. 
Obsoleting these old systems allows the development team to focus its 
limited resources to support those systems that are used by more people.

These targets can still be configured by using the --enable-obsolete 
option.  If no one steps forward to maintain these targets, they will be

deleted in a future gcc release.

Below, please find the complete list, in the form of GNU target 
triplets.  This has been extensively revised from the list that was 
originally posted in March.

If you feel strongly that support for one of these targets should not be

removed, please contact us by email to gcc@gcc.gnu.org.  Traditionally, 
GCC has been more receptive to requests that a particular target not be 
removed if a volunteer is available to maintain that target, so if 
you're interested in volunteering you should state that explicitly. 
Also, "there are 1000 of us using this machine heavily all day long and 
we were planning to upgrade to GCC 3.4" is probably more likely to sway 
the development team than "I think there is still one of those in my 
closet." :-)

All targets for these architectures have been obsoleted:
	d30v-*
	dsp16xx-*
	i370-*
	i960-*

Individual targets that have been obsoleted:
	i?86-moss-msdos
	i?86-*-moss*
	i?86-ncr-sysv4*
	i?86-*-netware
	i?86-*-freebsd2*
	i?86-*-freebsd*aout*
	i?86-*-linux*aout*
	i?86-*-linux*libc1*
	# This does not affect Interix3 support which remains.
	i?86-*-interix
	i?86-*-mach*
	i?86-*-udk*
	i?86-*-sysv[123]*
	i386-*-vsta

	m68k-hp-hpux*
	m68000-hp-hpux*
	m68k-*-sysv4*

	# This is only the a.out netbsd targets, the elf netbsd targets
	# remain.
	m68k*-*-netbsd*

	# This is only the default target, which is no longer useful.
	# The *BSD, Ultrix, and Sysv targets remain.
	vax-*-*
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Re: Obsoleting unmaintained targets

[Gerald Pfeifer]

On Wed, 3 Dec 2003, Aurélie wrote:
> unsubscribe !

Subscription and unsubscription are self-service:
  http://gcc.gnu.org/lists.html#subscribe

We do not subscribe anyone by ourselves, which means that you must have
subscribed yourself.

Gerald

Re: Obsoleting unmaintained targets

[Aurélie]

unsubscribe !
----- Original Message ----- 
From: "Jim Wilson" <wilson@specifixinc.com>
To: <gcc-announce@gcc.gnu.org>
Cc: <gcc@gcc.gnu.org>
Sent: Wednesday, December 03, 2003 12:18 AM
Subject: Obsoleting unmaintained targets


> In the GCC 3.4 release (still some time in the future), the GCC 
> developers are obsoleting a number of old unmaintained targets. 
> Obsoleting these old systems allows the development team to focus its 
> limited resources to support those systems that are used by more people.
> 
> These targets can still be configured by using the --enable-obsolete 
> option.  If no one steps forward to maintain these targets, they will be 
> deleted in a future gcc release.
> 
> Below, please find the complete list, in the form of GNU target 
> triplets.  This has been extensively revised from the list that was 
> originally posted in March.
> 
> If you feel strongly that support for one of these targets should not be 
> removed, please contact us by email to gcc@gcc.gnu.org.  Traditionally, 
> GCC has been more receptive to requests that a particular target not be 
> removed if a volunteer is available to maintain that target, so if 
> you're interested in volunteering you should state that explicitly. 
> Also, "there are 1000 of us using this machine heavily all day long and 
> we were planning to upgrade to GCC 3.4" is probably more likely to sway 
> the development team than "I think there is still one of those in my 
> closet." :-)
> 
> All targets for these architectures have been obsoleted:
> d30v-*
> dsp16xx-*
> i370-*
> i960-*
> 
> Individual targets that have been obsoleted:
> i?86-moss-msdos
> i?86-*-moss*
> i?86-ncr-sysv4*
> i?86-*-netware
> i?86-*-freebsd2*
> i?86-*-freebsd*aout*
> i?86-*-linux*aout*
> i?86-*-linux*libc1*
> # This does not affect Interix3 support which remains.
> i?86-*-interix
> i?86-*-mach*
> i?86-*-udk*
> i?86-*-sysv[123]*
> i386-*-vsta
> 
> m68k-hp-hpux*
> m68000-hp-hpux*
> m68k-*-sysv4*
> 
> # This is only the a.out netbsd targets, the elf netbsd targets
> # remain.
> m68k*-*-netbsd*
> 
> # This is only the default target, which is no longer useful.
> # The *BSD, Ultrix, and Sysv targets remain.
> vax-*-*
> -- 
> Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
> 
> 

Re: Obsoleting unmaintained targets

[Jim Wilson]

chewbaccathewookie@att.net wrote:
> Hello from Gregg C Levine
> Actually yes. I see a need for the Big Foot one, thats i370, and the Intel 
> i960. For example for the i960 I do have a processor here, been shopping for 
> a board for it, for a while now.  As for the i370 one, isn't that the core 
> for  building s/390 based kernel? There should be one for i390 instead then. 

The i960 gcc port has been broken for about 3 and a half years now, and 
the gdb support has already been deleted.  Maintaining a compiler port 
is a lot of work.  It isn't practical for us to maintain the port for 
one person who has one processor.  You can try using a gcc-2.x compiler 
for i960 work.  It should work fine.  It just won't have all of the new 
gcc features.  There are also binaries for a modified gcc toolchain 
available for download from the Intel web site.  (Or at least there used 
to be.)

There are i370 and s390 ports.  The i370 has been unmaintained for a 
long time.  The s390 port is the one that is used to build the s390 
toolchains.  It is not affected by this change.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Re: Obsoleting unmaintained targets

[Joel Sherrill]

chewbaccathewookie@att.net wrote:

>Hello from Gregg C Levine
>Actually yes. I see a need for the Big Foot one, thats i370, and the Intel 
>i960. For example for the i960 I do have a processor here, been shopping for 
>a board for it, for a while now.  As for the i370 one, isn't that the core 
>for  building s/390 based kernel? There should be one for i390 instead then. 
>Just my two cents.
>  
>
Someone more familiar with the i370/i390 distinction can explain the 
rationale behind that one.

The i960 has bene on the chopping block for a fairly long time and the 
Steering Committee has
made extra effort to attempt to find a maintainer.  No one appeared.  
The i960 port has been
broken for a long time.  See:

http://gcc.gnu.org/ml/gcc-bugs/2001-07/msg00257.html
http://gcc.gnu.org/ml/gcc-patches/2002-10/msg00359.html

In addition, it has already been obsoleted by gdb and that didn't cause 
much noise either. :)

So unless you are volunteering to fix gcc and gdb and maintain them by 
yourself, there isn't
much alternative.  Sorry.

--joel sherrill

>Gregg C Levine chewbaccathewookie atsign worldnet dot att dot net
>
>This signature was brought here by the Falcon.
>  
>
>>In the GCC 3.4 release (still some time in the future), the GCC 
>>developers are obsoleting a number of old unmaintained targets. 
>>Obsoleting these old systems allows the development team to focus its 
>>limited resources to support those systems that are used by more people.
>>
>>These targets can still be configured by using the --enable-obsolete 
>>option.  If no one steps forward to maintain these targets, they will be 
>>deleted in a future gcc release.
>>
>>Below, please find the complete list, in the form of GNU target 
>>triplets.  This has been extensively revised from the list that was 
>>originally posted in March.
>>
>>If you feel strongly that support for one of these targets should not be 
>>removed, please contact us by email to gcc@gcc.gnu.org.  Traditionally, 
>>GCC has been more receptive to requests that a particular target not be 
>>removed if a volunteer is available to maintain that target, so if 
>>you're interested in volunteering you should state that explicitly. 
>>    
>>
>
>  
>
>>Also, "there are 1000 of us using this machine heavily all day long and 
>>we were planning to upgrade to GCC 3.4" is probably more likely to sway 
>>the development team than "I think there is still one of those in my 
>>closet." :-)
>>
>>All targets for these architectures have been obsoleted:
>>	d30v-*
>>	dsp16xx-*
>>	i370-*
>>	i960-*
>>
>>Individual targets that have been obsoleted:
>>	i?86-moss-msdos
>>	i?86-*-moss*
>>	i?86-ncr-sysv4*
>>	i?86-*-netware
>>	i?86-*-freebsd2*
>>	i?86-*-freebsd*aout*
>>	i?86-*-linux*aout*
>>	i?86-*-linux*libc1*
>>	# This does not affect Interix3 support which remains.
>>	i?86-*-interix
>>	i?86-*-mach*
>>	i?86-*-udk*
>>	i?86-*-sysv[123]*
>>	i386-*-vsta
>>
>>	m68k-hp-hpux*
>>	m68000-hp-hpux*
>>	m68k-*-sysv4*
>>
>>	# This is only the a.out netbsd targets, the elf netbsd targets
>>	# remain.
>>	m68k*-*-netbsd*
>>
>>	# This is only the default target, which is no longer useful.
>>	# The *BSD, Ultrix, and Sysv targets remain.
>>	vax-*-*
>>-- 
>>Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
>>
>>    
>>
>
>  
>

Re: Obsoleting unmaintained targets

[chewbaccathewookie]

Hello from Gregg C Levine
Actually yes. I see a need for the Big Foot one, thats i370, and the Intel 
i960. For example for the i960 I do have a processor here, been shopping for 
a board for it, for a while now.  As for the i370 one, isn't that the core 
for  building s/390 based kernel? There should be one for i390 instead then. 
Just my two cents.
Gregg C Levine chewbaccathewookie atsign worldnet dot att dot net

This signature was brought here by the Falcon.
> In the GCC 3.4 release (still some time in the future), the GCC 
> developers are obsoleting a number of old unmaintained targets. 
> Obsoleting these old systems allows the development team to focus its 
> limited resources to support those systems that are used by more people.
> 
> These targets can still be configured by using the --enable-obsolete 
> option.  If no one steps forward to maintain these targets, they will be 
> deleted in a future gcc release.
> 
> Below, please find the complete list, in the form of GNU target 
> triplets.  This has been extensively revised from the list that was 
> originally posted in March.
> 
> If you feel strongly that support for one of these targets should not be 
> removed, please contact us by email to gcc@gcc.gnu.org.  Traditionally, 
> GCC has been more receptive to requests that a particular target not be 
> removed if a volunteer is available to maintain that target, so if 
> you're interested in volunteering you should state that explicitly. 

> Also, "there are 1000 of us using this machine heavily all day long and 
> we were planning to upgrade to GCC 3.4" is probably more likely to sway 
> the development team than "I think there is still one of those in my 
> closet." :-)
> 
> All targets for these architectures have been obsoleted:
> 	d30v-*
> 	dsp16xx-*
> 	i370-*
> 	i960-*
> 
> Individual targets that have been obsoleted:
> 	i?86-moss-msdos
> 	i?86-*-moss*
> 	i?86-ncr-sysv4*
> 	i?86-*-netware
> 	i?86-*-freebsd2*
> 	i?86-*-freebsd*aout*
> 	i?86-*-linux*aout*
> 	i?86-*-linux*libc1*
> 	# This does not affect Interix3 support which remains.
> 	i?86-*-interix
> 	i?86-*-mach*
> 	i?86-*-udk*
> 	i?86-*-sysv[123]*
> 	i386-*-vsta
> 
> 	m68k-hp-hpux*
> 	m68000-hp-hpux*
> 	m68k-*-sysv4*
> 
> 	# This is only the a.out netbsd targets, the elf netbsd targets
> 	# remain.
> 	m68k*-*-netbsd*
> 
> 	# This is only the default target, which is no longer useful.
> 	# The *BSD, Ultrix, and Sysv targets remain.
> 	vax-*-*
> -- 
> Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
> 

Obsoleting unmaintained targets

[Jim Wilson]

In the GCC 3.4 release (still some time in the future), the GCC 
developers are obsoleting a number of old unmaintained targets. 
Obsoleting these old systems allows the development team to focus its 
limited resources to support those systems that are used by more people.

These targets can still be configured by using the --enable-obsolete 
option.  If no one steps forward to maintain these targets, they will be 
deleted in a future gcc release.

Below, please find the complete list, in the form of GNU target 
triplets.  This has been extensively revised from the list that was 
originally posted in March.

If you feel strongly that support for one of these targets should not be 
removed, please contact us by email to gcc@gcc.gnu.org.  Traditionally, 
GCC has been more receptive to requests that a particular target not be 
removed if a volunteer is available to maintain that target, so if 
you're interested in volunteering you should state that explicitly. 
Also, "there are 1000 of us using this machine heavily all day long and 
we were planning to upgrade to GCC 3.4" is probably more likely to sway 
the development team than "I think there is still one of those in my 
closet." :-)

All targets for these architectures have been obsoleted:
	d30v-*
	dsp16xx-*
	i370-*
	i960-*

Individual targets that have been obsoleted:
	i?86-moss-msdos
	i?86-*-moss*
	i?86-ncr-sysv4*
	i?86-*-netware
	i?86-*-freebsd2*
	i?86-*-freebsd*aout*
	i?86-*-linux*aout*
	i?86-*-linux*libc1*
	# This does not affect Interix3 support which remains.
	i?86-*-interix
	i?86-*-mach*
	i?86-*-udk*
	i?86-*-sysv[123]*
	i386-*-vsta

	m68k-hp-hpux*
	m68000-hp-hpux*
	m68k-*-sysv4*

	# This is only the a.out netbsd targets, the elf netbsd targets
	# remain.
	m68k*-*-netbsd*

	# This is only the default target, which is no longer useful.
	# The *BSD, Ultrix, and Sysv targets remain.
	vax-*-*
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com