Hi,
Configuring valgrind results in the following error:
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/opt/sw/src/fink.build/valgrind-3.9.0-1/valgrind-3.9.0':
configure: error: C compiler cannot create executables
See `config.log' for more details
### execution of /tmp/fink.Is5Gt failed, exit code 77
### execution of /tmp/fink.XhN8G failed, exit code 77
This is not very informative, but the config log contains the
following:
configure:3552: $? = 0
configure:3541: gcc -v >&5
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin12.5.0
Thread model: posix
configure:3552: $? = 0
configure:3541: gcc -V >&5
clang: error: argument to '-V' is missing (expected 1 value)
clang: error: no input files
configure:3552: $? = 1
configure:3541: gcc -qversion >&5
clang: error: unknown argument: '-qversion'
[-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in
the future
clang: error: no input files
configure:3552: $? = 1
configure:3572: checking whether the C compiler works
configure:3594: gcc -Wno-long-long -I/opt/sw/include
-headerpad_max_install_names -L/opt/sw/lib -new_linker conftest.c >&5
clang: error: unknown argument: '-new_linker'
[-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in
the future
configure:3598: $? = 1
configure:3636: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "Valgrind"
| #define PACKAGE_TARNAME "valgrind"
| #define PACKAGE_VERSION "3.9.0"
| #define PACKAGE_STRING "Valgrind 3.9.0"
| #define PACKAGE_BUGREPORT "valgrind-us...@lists.sourceforge.net"
| #define PACKAGE_URL ""
| #define PACKAGE "valgrind"
| #define VERSION "3.9.0"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3641: error: in
`/opt/sw/src/fink.build/valgrind-3.9.0-1/valgrind-3.9.0':
configure:3643: error: C compiler cannot create executables
Could this be yet another instance of clang breaking things? I am
also worried about the "-V" error though... I am on Fink 0.36.4 so
this should not be an issue anymore, but I also see the failure above.
Here is the rest of the system info (all on Mac OS 10.8.5):
Distribution version: selfupdate-rsync Tue Apr 8 19:07:08 2014, 10.8, x86_64
Trees: local/main stable/main
Xcode.app: 5.1
Xcode command-line tools: 5.1.0.0.1.1393561416
Max. Fink build jobs: 8
Speaking of clang ugliness, I have a DMG for Xcode 5.0.2 and one for
the associated "command line tools for Mountain Lion - September
2013." Would it make sense to trash the current Xcode, replace it
with the above, refrain from ever updating the tinng, and so live
happily ever after (or until updating the OS)?
Advice is appreciated.
Best regards,
Stefan
--
If it was so, it might be; and if it were so, it would be; but as it
isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass
No HTML emails and proprietary attachments please <http://bruda.ca/ascii>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
