ARGHHHH! Please Help Me!!!!!

[Paladin9]

In osx, now whenever I try to use ./configure for anything is says "C compiler can not create executables".  I did not used to do this, it started doing it after I typed "whereis pkg-config".  What happened? Could anyone help me??

[preacher]

Im moving this to the mac forum.

[flap]

After you run configure, look at config.log for the error.

[Paladin9]

I did.  It does not tell me anything.

[flap]

It might mean something to me or someone else. What does it say?

[Paladin9]

Well it is really long so here is the end of the file:

oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define GLIB_BINARY_AGE 203
#define GLIB_INTERFACE_AGE 3
#define GLIB_MAJOR_VERSION 2
#define GLIB_MICRO_VERSION 3
#define GLIB_MINOR_VERSION 2
#define G_COMPILED_WITH_DEBUGGING "minimum"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""

configure: exit 77


Any help you could give me would be great.

[flap]

That doesn't really tell me anything. There should be some sort of error message in the log. Just look further up in the log where it's actually trying to do something (lines beginning with "configure:"). The last few messages will probably be error messages.

[Paladin9]

Maybe this will help:  

configure:2442: $? = 0
configure:2444: gcc -v </dev/null >&5
Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1495)
configure:2447: $? = 0
configure:2449: gcc -V </dev/null >&5
gcc: `-V' option must have argument
configure:2452: $? = 1
configure:2476: checking for C compiler default output
configure:2479: gcc    conftest.c  >&5
ld: /usr/lib/libSystem.dylib load command 5 unknown cmd field
configure:2482: $? = 1
configure: failed program was:
| #line 2455 "configure"
| /* confdefs.h.  */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define GLIB_MAJOR_VERSION 2
| #define GLIB_MINOR_VERSION 2
| #define GLIB_MICRO_VERSION 3
| #define GLIB_INTERFACE_AGE 3
| #define GLIB_BINARY_AGE 203
| #define G_COMPILED_WITH_DEBUGGING "minimum"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2521: error: C compiler cannot create executables
See `config.log' for more details.

[flap]

Have you recently upgraded OSX but not the developer tools?

[Paladin9]

Well, have not updated lately but I did recently install the old developent stuff that came with 10.0 along with the newer stuff.  I thought about that being the problem, but the thing is that this started happening right after I typed in "whereis pkg-config".  I did ./configure right before that without the c compiler error, and then right after I typed that whereis command in, it gave me the error.  Someone earlier told me to type the whereis command.  What does it do anyway?

[Paladin9]

Ok, I reinstalled the NEWER developer crap and now that damn error is gone, but I am still getting "pkg-config can not be found".  I already installed it by doing ./configure then make and then make install.  How do I get glib to know that pkg-config is on my system?

[hm_murdock]

Xcode kicks more ass than command line tools

[worker201]

Depends on where you put pkg-config and what configuration options the program you want to install takes.

Try"
./configure --help | more

which will tell you what configuration options there are.  It might let you give library paths or include paths.

If pkg-config is a library, you need to update your libraries.  Edit ld.conf to make sure the library path you are using (ie /usr/local/lib) is in there.  If not, add it.  Then run ldconfig to update the library paths.

Also, you could export a variable telling it where pkg-config is.  Use the setenv command for tcsh (on a Mac) or export for bash.

********

whereis is a command that sorta works like find.  It doesn't find normal files, though.  It only finds executable files and paths.  It's a completely harmless command, and did not fuck up your system.