Re: Installation of miscellaneous-1.0.11 package

[Sergei Steshenko]

--- On Tue, 4/5/11, Yoshi Yamada <address@hidden> wrote:

> From: Yoshi Yamada <address@hidden>
> Subject: Installation of miscellaneous-1.0.11 package
> To: address@hidden
> Date: Tuesday, April 5, 2011, 11:43 PM
> Hi everyone, 
> 
> Sorry for asking a basic question, but I was trying to
> install
> miscellaneous-1.0.11 package and it wouldn't work, with an
> error message as
> below: 
> 
> configure: error: in
> `/var/tmp/oct-FH3tCL/miscellaneous-1.0.11/src':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> the configure script returned the following error: checking
> for gcc...
> /usr/bin/gcc-4.2
> checking whether the C compiler works... no
> error: called from `pkg>configure_make' in file
> /Applications/Octave.app/Contents/Resources/share/octave/3.4.0/m/pkg/pkg.m
> near line 1320, column 9
> error: called from:
> error:  
> /Applications/Octave.app/Contents/Resources/share/octave/3.4.0/m/pkg/pkg.m
> at line 783, column 5
> error:  
> /Applications/Octave.app/Contents/Resources/share/octave/3.4.0/m/pkg/pkg.m
> at line 354, column 9
> 
> My working environment is: 
> Mac OS X 10.6.7 (X-code already installed)
> Octave-3.4.0
> 
> Could you tell me how to fix this (and where I can find
> 'config.log' file)?  
> Thank you in advance for your kind help! 
> 
> Best wishes, 
> Yoshi
> 
> --
> View this message in context: 
> http://octave.1599824.n4.nabble.com/Installation-of-miscellaneous-1-0-11-package-tp3430036p3430036.html
> Sent from the Octave - General mailing list archive at
> Nabble.com.
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave
> 

The "C compiler cannot create executables" message is not quite precise.

What it actually means is that your "C" compiler with the setting provided
by you and 'configure' cannot create executables. E.g. if for whatever
reason '-lfoo' is given, and no libfoo.* can be found by linker, the
linking part will fail and you'll get the message you've got.

You really need to have a look into 'config.log' - in such cases you can
find the full command line and the failed test program which caused the
failure.

There is no common/generic answer for this error message.

Regards,
  Sergei.