Changes between Initial Version and Version 2 of Ticket #14213
- Timestamp:
- Feb 7, 2008, 5:46:47 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14213
- Property Cc afb@… nox@… added
-
Property
Summary
changed from
help2man-1.36.4 configure fails as compiler cannot create executable
toContent of configure.cc variable is sometimes duplicated.
-
Ticket #14213 – Description
initial v2 2 2 3 3 Most of the details of the bug are in the email, but the highlight is this: 4 when configuring help2man-1.36.4, the compile doesn't finish as $(CC) has been doubly defined as "CC='/usr/bin/gcc-4.0 /usr/bin/gcc-4.0'"This eventually throws off the linker, and fails the configure.4 when configuring help2man-1.36.4, the compile doesn't finish as $(CC) has been doubly defined as `CC='/usr/bin/gcc-4.0 /usr/bin/gcc-4.0'` This eventually throws off the linker, and fails the configure. 5 5 6 6 There's an additional problem of the gcc -V flag not working. Looks like within OS X, the lowercase "v" must be used, if the intent is to extract the version of gcc in use. … … 31 31 My builds have been failing with the following info: 32 32 33 {{{ 33 34 ---> Configuring help2man 34 35 Error: Target org.macports.configure returned: configure failure: shell … … 43 44 compiler cannot create executables 44 45 See `config.log' for more details. 46 }}} 45 47 46 48 Having looked through the config.log, I noticed something peculiar. 47 49 50 {{{ 48 51 ac_cv_env_CC_value='/usr/bin/gcc-4.0 /usr/bin/gcc-4.0' 52 }}} 49 53 50 54 and 51 55 56 {{{ 52 57 CC='/usr/bin/gcc-4.0 /usr/bin/gcc-4.0' 58 }}} 53 59 54 The result is that $CCis doubly defined which seems the screw up the60 The result is that `$CC` is doubly defined which seems the screw up the 55 61 linker, as is evidenced here: 56 62 63 {{{ 57 64 configure:1632: $? = 1 58 65 configure:1655: checking for C compiler default output file name … … 62 69 the dynamic link editor, is not relocatable by the static link editor again 63 70 collect2: ld returned 1 exit status 71 }}} 64 72 65 73 I also noticed that the "-V" flag for gcc-4.0 is causing an error. 66 74 75 {{{ 67 76 configure:1629: /usr/bin/gcc-4.0 /usr/bin/gcc-4.0 -V </dev/null >&5 68 77 gcc-4.0: argument to `-V' is missing 78 }}} 69 79 70 80 I did attempt to do the configure and make manually from directly within the … … 72 82 happen when I run: 73 83 84 {{{ 74 85 sudo port install rb-rubygems. 86 }}} 75 87 76 88 I wouldn't have necessarily thought this was a bug (maybe double referencing