* c30 on rc3 broken
@ 2000-06-12 11:50 Joel Sherrill
2000-06-12 13:39 ` Philip Blundell
0 siblings, 1 reply; 4+ messages in thread
From: Joel Sherrill @ 2000-06-12 11:50 UTC (permalink / raw)
To: binutils
I can't get c30-coff or tic30-coff to configure. :(
.../configure --target=c30-coff results in this:
*** BFD does not support target c30-coff.
*** Look in bfd/config.bfd for supported targets.
Configure in /usr1/rtems/tmp/b-newc4x/b-b/opcodes failed, exiting.
.../configure --target=tic30-coff results in this:
Configuring for a i686-pc-linux-gnu host.
Invalid configuration `tic30-coff': machine `tic30' not recognized
Unrecognized target system name tic30-coff.
Any ideas?
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c30 on rc3 broken
2000-06-12 11:50 c30 on rc3 broken Joel Sherrill
@ 2000-06-12 13:39 ` Philip Blundell
[not found] ` <395771C5.7911F327@OARcorp.com>
0 siblings, 1 reply; 4+ messages in thread
From: Philip Blundell @ 2000-06-12 13:39 UTC (permalink / raw)
To: joel.sherrill; +Cc: binutils
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
>.../configure --target=c30-coff results in this:
>
>*** BFD does not support target c30-coff.
>*** Look in bfd/config.bfd for supported targets.
>Configure in /usr1/rtems/tmp/b-newc4x/b-b/opcodes failed, exiting.
>
>.../configure --target=tic30-coff results in this:
>
>Configuring for a i686-pc-linux-gnu host.
>Invalid configuration `tic30-coff': machine `tic30' not recognized
>Unrecognized target system name tic30-coff.
Looks like config.sub lossage. :-(
Try `c30-foo-coff'.
p.
[-- Attachment #2: pgp00000.pgp --]
[-- Type: text/plain, Size: 816 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
>.../configure --target=c30-coff results in this:
>
>*** BFD does not support target c30-coff.
>*** Look in bfd/config.bfd for supported targets.
>Configure in /usr1/rtems/tmp/b-newc4x/b-b/opcodes failed, exiting.
>
>.../configure --target=tic30-coff results in this:
>
>Configuring for a i686-pc-linux-gnu host.
>Invalid configuration `tic30-coff': machine `tic30' not recognized
>Unrecognized target system name tic30-coff.
Looks like config.sub lossage. :-(
Try `c30-foo-coff'.
p.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 (debian)
iD8DBQE5RT9+VTLPJe9CT30RArtgAKC1VSWSFy3PdnKGYXvPUM3zPpk8vQCfVLEq
jpGGw9kkMbaEGlqrCOe+8RE=
=wRZm
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c30 on rc3 broken
[not found] ` <395771C5.7911F327@OARcorp.com>
@ 2000-06-26 11:52 ` Philip Blundell
2000-06-27 9:49 ` Joel Sherrill
0 siblings, 1 reply; 4+ messages in thread
From: Philip Blundell @ 2000-06-26 11:52 UTC (permalink / raw)
To: joel.sherrill; +Cc: binutils
>I have been away on vacation and wondered if this was
>fixed.
Not yet.
>> >.../configure --target=c30-coff results in this:
>> >
>> >*** BFD does not support target c30-coff.
>> >*** Look in bfd/config.bfd for supported targets.
>> >Configure in /usr1/rtems/tmp/b-newc4x/b-b/opcodes failed, exiting.
>> >
>> >.../configure --target=tic30-coff results in this:
>> >
>> >Configuring for a i686-pc-linux-gnu host.
>> >Invalid configuration `tic30-coff': machine `tic30' not recognized
>> >Unrecognized target system name tic30-coff.
These two need to be fixed in config.sub. The problem with ld is that it
only recognizes the `tic30-' spelling. I guess someone should settle on one
or other, assuming that c30- and tic30- really are equivalents.
p.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c30 on rc3 broken
2000-06-26 11:52 ` Philip Blundell
@ 2000-06-27 9:49 ` Joel Sherrill
0 siblings, 0 replies; 4+ messages in thread
From: Joel Sherrill @ 2000-06-27 9:49 UTC (permalink / raw)
To: Philip Blundell; +Cc: binutils
Philip Blundell wrote:
> >> >.../configure --target=c30-coff results in this:
> >> >
> >> >*** BFD does not support target c30-coff.
> >> >*** Look in bfd/config.bfd for supported targets.
> >> >Configure in /usr1/rtems/tmp/b-newc4x/b-b/opcodes failed, exiting.
> >> >
> >> >.../configure --target=tic30-coff results in this:
> >> >
> >> >Configuring for a i686-pc-linux-gnu host.
> >> >Invalid configuration `tic30-coff': machine `tic30' not recognized
> >> >Unrecognized target system name tic30-coff.
>
> These two need to be fixed in config.sub. The problem with ld is that it
> only recognizes the `tic30-' spelling. I guess someone should settle on one
> or other, assuming that c30- and tic30- really are equivalents.
I have gotten c30- and tic30- to work now. But the bigger issue
is settling on a real name. gcc uses c4x-. The older patches
from the gcc-c40 group (Michael Hayes, et. al.) use c4x-.
I can provide a patch if we can settle on a direction. I hate to
add support for 3 name variations of a new target unless there is
good reason. :)
> p.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-06-27 9:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-06-12 11:50 c30 on rc3 broken Joel Sherrill
2000-06-12 13:39 ` Philip Blundell
[not found] ` <395771C5.7911F327@OARcorp.com>
2000-06-26 11:52 ` Philip Blundell
2000-06-27 9:49 ` Joel Sherrill
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).