GNU bug report logs - #8694
Configure on mips

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 8694 in the body.
You can then email your comments to 8694 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "James William Cronin" <jamescronin <at> doctors.org.uk>
To: bug-automake <at> gnu.org
Subject: Configure on mips
Date: Wed, 18 May 2011 19:00:54 +0100

When running automake generated configure scripts on an 
embeded mips based moded box (the Humax HD T2) - see 
www.hummypkg.org the generated make files contain a two 
letter addition to all variables followed by an @. (e.g. 
LL@, KK@ ir@ etc) The two additional letters seem to have 
some (although not uniformaly) resembelance to the 
preceding text.

Its basicly running busybox ontop of linux kernal 2.6.18

I am only passing --build=mips-unknown-linux-gnu to the 
scrip.

James

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Daniel Herring <dherring <at> tentpost.com>
To: James William Cronin <jamescronin <at> doctors.org.uk>
Cc: 8694 <at> debbugs.gnu.org, bug-automake <at> gnu.org
Subject: Re: bug#8694: Configure on mips
Date: Wed, 18 May 2011 23:47:40 -0400 (EDT)

On Wed, 18 May 2011, James William Cronin wrote:

> When running automake generated configure scripts on an embeded mips based 
> moded box (the Humax HD T2) - see www.hummypkg.org the generated make files 
> contain a two letter addition to all variables followed by an @. (e.g. LL@, 
> KK@ ir@ etc) The two additional letters seem to have some (although not 
> uniformaly) resembelance to the preceding text.
>
> Its basicly running busybox ontop of linux kernal 2.6.18
>
> I am only passing --build=mips-unknown-linux-gnu to the scrip.

Configure scripts are made by autoconf, not automake...

Look in a Makefile.in (next to a Makefile).  Does it have messed up 
variables?  If so, then automake is the culprit.  If not, then I'd guess 
the sed magic in config.status is messed up.

For an automake problem, the output of 'automake --version' would help. 
For a configure problem, the output of './configure --version' would help.

It also wasn't clear whether you are running autoconf and automake on the 
mips box or simply running ./configure and make.

- Daniel

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Daniel Herring <dherring <at> tentpost.com>
Cc: bug-autoconf <at> gnu.org, 8694 <at> debbugs.gnu.org, bug-automake <at> gnu.org,
	James William Cronin <jamescronin <at> doctors.org.uk>
Subject: Re: bug#8694: Configure on mips
Date: Sun, 08 Jan 2012 10:36:11 +0100

tags 8694 + moreinfo
tags 8694 + notabug
close 8694
thanks

Reference:
  <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8694>

On 05/19/2011 05:47 AM, Daniel Herring wrote:
> On Wed, 18 May 2011, James William Cronin wrote:
> 
>> When running automake generated configure scripts on an embeded mips
>> based moded box (the Humax HD T2) - see www.hummypkg.org the generated
>> make files contain a two letter addition to all variables followed by
>> an @. (e.g. LL@, KK@ ir@ etc) The two additional letters seem to have
>> some (although not uniformaly) resembelance to the preceding text.
>>
>> Its basicly running busybox ontop of linux kernal 2.6.18
>>
>> I am only passing --build=mips-unknown-linux-gnu to the scrip.
> 
> Configure scripts are made by autoconf, not automake...
> 
> Look in a Makefile.in (next to a Makefile).  Does it have messed up
> variables?  If so, then automake is the culprit.  If not, then I'd
> guess the sed magic in config.status is messed up.
>
> For an automake problem, the output of 'automake --version' would help.
> For a configure problem, the output of './configure --version' would
> help.
> 
> It also wasn't clear whether you are running autoconf and automake on
> the mips box or simply running ./configure and make.
> 
> - Daniel
> 
No answer after several months, so I assume with Daniel that the problem
was either an usage error or an autoconf issue (I'm CC:ing bug-autoconf
in case they are interested in taking a deeper look into the this).

I'm closing this bug report for what concerns automake.  Feel free to
re-open it if you still have reasons to suspect automake is the culprit
here.

Thanks,
  Stefano

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.