On Sun, Mar 24, 2002 at 03:24:42PM -0600, Chris Devers wrote:
> On Sun, 24 Mar 2002, Ben Hines wrote:
>
> > At 2:59 PM -0600 3/24/02, John Melby wrote:
> >
> > >>checking whether the C compiler (cc ) works... no
> > >>configure: error: installation or configuration problem: C compiler
> > >>cannot create executables.
> > >
> > >However, when I use cc to compile a C program, everything works perfectly.
> > >
> > >Is it possible that only you and I are having this problem? Or is
> > >something rotten in the world of XFree86dom?
> >
> > You likely need the December 2001 devtools, not the ones that came with OS X.
>
> When this came up before, he swore up & down that he was using the current
> [Dec] version of the devtools. If that's really the case -- and I still
> have my doubts, but John is the one that would know -- then I'm wondering
> if something else was installed that mucked around with things. What, I
> have no idea. GNU-Darwin? MacGimp? Beats me, but the signature of this
> problem really does point to a missing or corrupted devtools installation.
>
> The error lines above come from the './configure' phase of building,
> right? And configure scripts, as far as I know, interact with the system's
> autoconf command/library/thingy. So *maybe* there's a problem there, but
> again I'm not quite sure what. Did you try installing Fink's "autoconf",
> and did it work? Can you download & build other autoconf/configure using
> packages? (Before using Fink, I had installed my own copies of Vim, Pine,
> and a couple of others -- maybe something like that is worth a shot over
> in /usr/local.)
>
> Something about the interaction between autoconf (etc) and cc/gcc isn't
> right, but I can't say which end is causing the problem, or if it's
> something that comes in between them. You [John] say that you can get
> programs with straight cc to work: are these "hello world" type programs
> or can you do anything more complex than that? Rather than righteous
> indignation, maybe you could offer more diagnostic details... :)
>
I seem to remember from John's original posting that configure found a
gcc in the path, and that would definitely indicate that there is another
executable around which is probably not from the current devtools.
John, I would suggest doing a `which gcc`, and if that returns anything
that is not a symlink to /usr/bin/cc, it likely is the cause of the
problems. Try a 'cmp $(which cc) /usr/bin/cc' to see if these are
actually different executables, or find out where it comes from
(GNU-Darwin in fact comes to mind), but if in doubt I would just
remove it or at least move it out of the way.
All this is assuming that the above error message came from Wayne's
posting, who might in fact have to check his devtools version.
HTH,
Derek
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
