From: Bart Veer <bartv@redhat.com>
To: mmacmillan@draper.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] ECOS build/config problems under Sparc Solaris 2.5.1
Date: Wed, 13 Sep 2000 05:59:00 -0000 [thread overview]
Message-ID: <200009131259.NAA32520@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <4.2.0.58.20000913081236.00a24410@imap.draper.com>
>>>>> "Mike" == Mike MacMillan <mmacmillan@draper.com> writes:
Mike> Hello,
Mike> I am having build/config problems of ECOS host tools on solaris 2.5.1.
Mike> I am running top-level configure script to supposedly build ecosconfig
Mike> command line tool.
Mike> The following output is displayed:
Mike> checking host system type... sparc-sun-solaris2.5.1
Mike> checking for a BSD compatible install...
Mike> /export/home/mjm1431/ecos/ecos-1.3.1/to
Mike> ols/src/install-sh -c
Mike> checking whether build environment is sane... yes
Mike> checking whether make sets ${MAKE}... yes
Mike> checking for working aclocal... missing
Mike> checking for working autoconf... missing
Mike> checking for working automake... missing
Mike> checking for working autoheader... missing
Mike> checking for working makeinfo... found
Mike> checking whether to enable maintainer-specific portions of Makefiles...
Mike> no
Mike> checking whether make sets ${MAKE}... (cached) yes
Mike> checking for Cygwin environment... no
Mike> checking for gcc... gcc
Mike> checking whether the C compiler (gcc ) works... no
Mike> configure: error: installation or configuration problem: C compiler
Mike> cannot creat
Mike> e executables.
Mike> Has anyone tried to do this on a solaris machine?
There was some discussion of Solaris builds just yesterday, see the
archives at http://sources.redhat.com/ml/ecos-discuss/
Mike> Any suggestions are welcome!
The message indicates that you do not have a working gcc installation.
At this stage in the configure script it will generate the following
file conftest.c:
#line 1044 "configure"
#include "confdefs.h"
main(){return(0);}
where confdefs.h is probably an empty file, and try to compile and run
it using something like:
gcc -o conftest conftest.c
conftest
Somewhere along the way this fails, so as far as the configure script
is concerned you do not have a working gcc installation. Something
like the 2.95.2 release should be fine, see http://gcc.gnu.org/ for
details.
Bart
prev parent reply other threads:[~2000-09-13 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 5:13 Mike MacMillan
2000-09-13 5:59 ` Bart Veer [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=200009131259.NAA32520@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=mmacmillan@draper.com \
/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).