public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: leandro@av.it.pt
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ECOS Building tools under Linux 6.2
Date: Fri, 13 Oct 2000 14:50:00 -0000	[thread overview]
Message-ID: <39E78316.F6B0ABCE@redhat.com> (raw)
In-Reply-To: <NEBBIMHEEKJOHEHGOOIFEEDOCAAA.leandro@av.it.pt>

Leandro Vieira wrote:
> 
>  Hello.
> 
>  I had completed building tools under windows NT with binutils-2.10,gcc
>  2.95.2 and gdb 5.0. and had also applyed the patch ecos-gcc-2952.pat to
> gcc.
>  This process it's the same that i have been try to do under Linux 6.2
> without sucess.
>  So i moved that i had in Windows NT to correspondent folder in Linux.
>  Now i'm trying to build the tools for Synthetic Linux target:
>  i followed all steps in agreement with document.
>  in step 3 of document, when i try configure GCC i get the follow error
> message, it's the only
>  message that i get:
> 
>          *** connot find config.sub.

You moved the sources directly? At a guess config.sub doesn't have the
execute bit, so do chmod +x config.sub. Also check that config.sub is spelt
in lower case. And failing that, try doing yourself what the configure
script would do, which would be

/bin/sh /src/gcc/gcc-2.95.2/config.sub sun4

which should output:

sparc-sun-sunos4.1.1

Also I hope that whatever way you copied it wouldn't allow any CRLFs in -
it's something to watch out for if you have any more problems.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

      reply	other threads:[~2000-10-13 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-13 13:41 Leandro Vieira
2000-10-13 14:50 ` Jonathan Larmour [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39E78316.F6B0ABCE@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=leandro@av.it.pt \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).