On screen I get:-
checking for gcc.....no
checking for cc....yes
checking for C compiler default output file name... configure: error:
C compiler cannot create executables
See 'config.log' for more details
And here is config.log:-
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure
## --------- ##
## Platform. ##
## --------- ##
hostname = sardis
uname -m = i86pc
uname -r = 5.9
uname -s = SunOS
uname -v = Generic_118559-11
/usr/bin/uname -p = i386
/bin/uname -X = System = SunOS
Node = sardis
Release = 5.9
KernelID = Generic_118559-11
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 1
/bin/arch = i86pc
/usr/bin/arch -k = i86pc
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/sbin
PATH: /usr/bin
PATH: /usr/dt/bin
PATH: /usr/openwin/bin
PATH: /bin
PATH: /usr/ucb
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1361: checking for gcc
configure:1390: result: no
configure:1441: checking for cc
configure:1457: found /usr/ucb/cc
configure:1467: result: cc
configure:1631: checking for C compiler version
configure:1634: cc --version </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:1637: $? = 1
configure:1639: cc -v </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:1642: $? = 1
configure:1644: cc -V </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:1647: $? = 1
configure:1670: checking for C compiler default output file name
configure:1673: cc conftest.c >&5
/usr/ucb/cc: language optional software package not installed
configure:1676: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:1715: error: C compiler cannot create executables
See `config.log' for more details.
## ---------------- ##
## Cache variables. ##
## ---------------- ##
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_prog_ac_ct_CC=cc
## ----------------- ##
## Output variables. ##
## ----------------- ##
BINFLOPPYD=''
CC='cc'
CFLAGS=''
CPP=''
CPPFLAGS=''
DEFS=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
FLOPPYD=''
HOST_ID=''
INSTALL_DATA=''
INSTALL_INFO=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LN_S=''
LTLIBOBJS=''
MACHDEPLIBS=''
OBJEXT=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
SHELL='/bin/bash'
SHLIB=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=''
ac_ct_CC='cc'
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='${prefix}/share'
exec_prefix='NONE'
extraincludedir=''
extralibdir=''
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='${prefix}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target=''
target_alias=''
target_cpu=''
target_os=''
target_vendor=''
## ----------- ##
## confdefs.h. ##
## ----------- ##
#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
configure: exit 77
You don't have a compiler installed. /usr/ucb/cc can wrap a compiler
AFAIK. Get Sun Studio on Sun's website for free or download a gcc from
either blastwave.org or sunfreeware.com and adjust your PATH accordingly...
HTH,
Thomas
>Trying to ./configure mtools.
>On screen I get:-
>checking for gcc.....no
>checking for cc....yes
>checking for C compiler default output file name... configure: error:
>C compiler cannot create executables
>See 'config.log' for more details
>And here is config.log:-
You will want to install Sun's C compiler or add the appropriate
directory to the front of $PATH (/opt/SUNWspro/bin).
If you dont;' have that directory, you need to download either Sun's
latest C compiler or gcc.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
1. Download and install Sun Studio compilers
http://developers.sun.com/sunstudio/downloads/index.jsp
2. Get rid of /usr/ucb in your PATH; replace it with /opt/SUNWspro/bin
3. Add /usr/ccs/bin to the PATH as well.
$ env PATH=/usr/bin:/usr/sbin:/usr/ccs/bin:/opt/SUNWspro/bin ./configure
May need to set CC, CFLAGS, LDFLAGS and other environment variables
per the docs and ./configure --help.
John
groe...@acm.org
I've downloaded and installed gcc from sunfreeware now (and adjusted
the PATH) and it works fine now.
> I've downloaded and installed gcc from sunfreeware now (and adjusted
> the PATH) and it works fine now.
I wonder what the output of
$ /usr/sfw/bin/gcc -v
might be. If you installed the complete distribution you already had a
working C compiler on that system.
On Solaris 9? Really? I thought gcc was first included in Solaris 10 FCS...
> Dave Uhring schrieb:
>> I wonder what the output of
>>
>> $ /usr/sfw/bin/gcc -v
>>
>> might be. If you installed the complete distribution you already had a
>> working C compiler on that system.
>>
>>
> On Solaris 9? Really? I thought gcc was first included in Solaris 10
> FCS...
Well, shoot. My brain is fading again. I guess that I had installed it
from the Companion CD.
4. For f*!$'s sake learn to use a search engine before posting questions
that have already been asked hundreds of times.
A bientot
Paul
--
Paul Floyd http://paulf.free.fr
Please feel free to ignore my post if its not of interest to you...
So, did you spend 30 seconds of your own time doing some research
before asking here?
Thought not.
It's my hope that if I'm mildly rude, either you'll go away and not be a
bother any more, or you'll take the hint and learn how to answer
elementary questions by yourself (e.g., by copy/pasting error messages
into Google).
A bientot peut-etre
Paul,
Yes, I did.
I really dont understand why people like you get so annoyed at
questions. Surely this is what usenet is for, the exchange of
information? If everything was answered by searching on google then
there'd be no need of usenet would there because nobody would ever
post there.
Also, like I said, its not as if I emailed you directly and you were
forced to read my post. The header was quite self-explanatory so you
could have ignored it.
Then again, I do agree with you to some extent where the same question
is asked every day in a usernet group. Its just that in this
circumstance, I dont think the question was that common.
what did you try? I get quite a few hits on Solaris FAQ
How about this: C Compiler cannot create executables
I get almost 63,000 hits
> I really dont understand why people like you get so annoyed at
> questions. Surely this is what usenet is for, the exchange of
> information?
FAQs arent information - they are re-treads. Whats the use of
a Usenet group that repeats itself over and over? People who actually
could help you eventually stop reading the group. Then it becomes
a blind leading the blind or spam repository newsgroup.
I do long sometimes for the days of S Howard...
> If everything was answered by searching on google then
> there'd be no need of usenet would there because nobody would ever
> post there.
No need for you to post here perhaps?? : >
> Also, like I said, its not as if I emailed you directly and you were
> forced to read my post. The header was quite self-explanatory so you
> could have ignored it.
Unfortunately killfiling doesnt work well with on google groups which
Im forced to
use most of the time. Also the number of 'big nut' folks like you
appearing on the
scene the last couple of years make a kill file grow in an
exponentional fashion in a matter of weeks.
Another thing to maintain : /
> Then again, I do agree with you to some extent where the same question
> is asked every day in a usernet group. Its just that in this
> circumstance, I dont think the question was that common.
YOU dont think? Of course it is or it wouldnt be a FAQ would it?
When I tried pasting the message into Google, the first 4 hits, whilst
rather dated, all explained the problem.
The first sentence from the first hit:
"There is no C compiler included in Solaris 2.x."
I'm too old and have been using usenet for too long to have much
patience for questions like this.
I still hope that you will persist and continue to contribute to this
newsgroup.
A bientot
Paul
Following on from some of the replies in this thread, I agree that you
are right.
Sorry, I didnt do enough research before asking the question. Like
some have quite correctly said, its not too difficult to find an
answer to this question.
Had no intention of upsetting people or taking people on this forum
for granted. Please accept my apologies.