Bug 10180 - Some changes on autobuilder caused config.guess to determine chost wrong
: Some changes on autobuilder caused config.guess to determine chost wrong
Status: RESOLVED WORKSFORME
Product: maemo.org Website
Autobuilder
: unspecified
: All Maemo
: Unspecified blocker (vote)
: ---
Assigned To: Niels Breet
: repositories@maemo.bugs
:
:
:
:
  Show dependency tree
 
Reported: 2010-05-16 10:16 UTC by Marat Radchenko
Modified: 2010-07-24 12:48 UTC (History)
2 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Marat Radchenko (reporter) 2010-05-16 10:16:13 UTC
1. enable extras-devel repo
2. apt-get source sflphone-common=0.9.7~ppa1~jaunty-maemo8
3. Increase version number (dch -i)
4. Prepare package for upload (fakeroot dpkg-buildpackage -sa -S)
5. Upload it (dput)

Expected: package builds again
Actual: package fails to build:
https://garage.maemo.org/builder/fremantle/sflphone-common_0.9.7~ppa1~jaunty-maemo9/armel.build.log.FAILED.txt

Root of problem: something causes libs/pjproject/config.guess determine chost
as  arm-unknown-linux-gnueabi (and not arm-unknown-linux-gnu as it was before).

Reproducibility: 100%

This bug doesn't happen in maemo sdk, so it's something wrong in autobuilder
setup.
Comment 1 Javier S. Pedro 2010-05-17 20:03:19 UTC
Note that the -gnueabi triplet is the more recent one, so in a sense it is
desirable to start using it on the autobuilder. 

Can you edit the package so that it always uses the config.guess from the host?
As it is now, it's using its own config.guess for the first configure run and
host's config.guess for the second (pjproject) run. This causes conflicting
results as the shipped config.guess is from 2005 (thus -gnu triplet) while the
autobuilder config.guess is from 2009 (thus -gnueabi triplet). 

You could either ship both config.guess files (and thus get consistent -gnu
results), or ship none (and thus get consistent -gnueabi results*).

I've seen that you're cp -f /usr/share/misc/config.guess config.guess at
dh_clean time. Doing that before running autogen.sh at configure time seemingly
fixes it. I need to read what the Debian policy exactly says about this.

(*There's also a bug around, since automake wants to copy its own automake-1.8
version of the file).
Comment 2 Marat Radchenko (reporter) 2010-07-24 12:48:32 UTC
Okay, I fixed my package.