[ python-Bugs-1578513 ] 2.4.4c1 will not build when cross compiling

[SourceForge.net]

Bugs item #1578513, was opened at 2006-10-16 23:27
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1578513&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: smithj (smithj_rpath)
Assigned to: Anthony Baxter (anthonybaxter)
Summary: 2.4.4c1 will not build when cross compiling

Initial Comment:
When trying to build 2.4.4c1 with cross-compiling, I
get the following 
error.

checking for /dev/ptmx... configure: error: cannot
check for file 
existence when cross compiling

./config.log:configure:20566: checking for /dev/ptmx
./config.log:configure:20572: error: cannot check for
file existence 
when cross compiling

This does not occur with 2.4.3.

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2006-10-17 21:00

Message:
Logged In: YES 
user_id=21627

Committed into 2.5 as 52362, and the trunk as 52363.

----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2006-10-17 18:11

Message:
Logged In: YES 
user_id=29957

Yeah, this is the ubuntu version of autoconf, oh well. I
don't have time right now to mess around with installing a
new autoconf (it's late, and I have a release in the morning). 

Checked into release24-maint as r52358, will be part of
2.4.4 (and 2.5.1 and 2.6 when I forward-port it). Leaving
open as a reminder.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2006-10-17 17:37

Message:
Logged In: YES 
user_id=21627

The patch looks fine to me. Of course, the check result is
still bogus for cross-compilation (so it doesn't, and really
can't, "work"), as we cannot know whether /dev/something
exists on the target machine.

As for regenerating configure: it should work fine if you
install a stock autoconf 2.59 (I typically have one in
~/ac259). If you happen to use a Debian-or-Redhat-modified
one, regeneration will often include unrelated changes.

As there really isn't a better way to deal with it, this
should then also be forward-ported to 2.5 and 2.6.

----------------------------------------------------------------------

Comment By: smithj (smithj_rpath)
Date: 2006-10-17 16:38

Message:
Logged In: YES 
user_id=1622486

Yes, that patch does fix the issue. Thank you.

----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2006-10-17 15:21

Message:
Logged In: YES 
user_id=29957

Ok, this revision is definitely the problem - it switched
from using our own test to autoconf's AC_CHECK_FILE. This
breaks things. Yay. :-/

Looking closer - we used to use our own test -e check.
autoconf uses test -r. The attached patch reverses that fix,
and changes back to our own test, using test -r instead.

Can you please test this? Martin, can you check this out? I
had to hand-edit the patch, because autoconf on this box
spat out a vast number of extra pointless changes. 


----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2006-10-17 14:50

Message:
Logged In: YES 
user_id=29957

Goody - autoconf debugging, my absolute favourite!

r50983 | martin.v.loewis | 2006-07-31 00:11:03 +1000 (Mon,
31 Jul 2006) | 3 lines

Drop usage of test -e in configure as it is not portable.
Fixes #1439538



----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2006-10-17 00:27

Message:
Logged In: YES 
user_id=44345

Boosting this and at least provisionally assigning to Anthony since it's related to 
a change between 2.4.3 and 2.4.4c1.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1578513&group_id=5470