[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to debug autoconf issues?

From: m h
Subject: Re: How to debug autoconf issues?
Date: Wed, 11 Jan 2006 15:48:04 -0800

On 1/11/06, Ralf Wildenhues <address@hidden> wrote:
> Hi Matt,
> * m h wrote on Wed, Jan 11, 2006 at 08:26:02PM CET:
> >
> > I'm working with a few of the alt-gentoo developers who are trying to
> > get portage (the gentoo linux build framework) to work on non-gentoo
> > systems.
> (I hope they understand that their libtool patches need to go on other
> systems.. oh sorry, you're not the one to rant to.  I was thinking out
> loud.)

I'm assumming you mean they should send patches upstream to you?  I
will certainly inform the group of this.

> > I'm running into configure issues that I can't seem to resolve.  (I
> > wouldn't call myself a C programmer.  I'm much more comfy in python.
> > But I can get around a linux system).  My issue is that when portage
> > runs the "./configure" I get errors like the following:
> OK.  Much more interesting are config.log contents (and much more
> detailed, so if you really need to post it all, please pack it).
> Some hints:

I've attached a zipped config.log.

> > checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
> So you used --host or the like, to announce cross-compilation.  In that
> case a $host_alias-prefixed compiler will be preferred.  And is found
> here.

Here's the configure command:
./configure \
--host=i686-pc-linux-gnu  \
are/info \

> > checking for C compiler default output... a.out
> > checking whether the C compiler works... yes
> > checking whether we are cross compiling... no
> (i.e., $host = $build).
> > checking for suffix of executables...
> > checking for suffix of object files...
> This is suspicious.  config.log should be able to tell more.


Thanks for your response.   I've attached my config.log.  Please let
me know what areas to look at for hints as to my issues.



Attachment: config.log.gz
Description: GNU Zip compressed data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]