The following reply was made to PR os-linux/2527; it has been noted by GNATS.
From: Allanah Myles <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-linux/2527: Incorrect assumptions in the 1.3.0 Configure script
for Linux 2.0.x/libc5 (non-glibc2) systems.
Date: Mon, 3 Aug 1998 13:55:14 -0400
On 1998.08.03, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> [In order for any reply to be added to the PR database, ]
> [you need to include <[EMAIL PROTECTED]> in the Cc line ]
> [and leave the subject line UNCHANGED. This is not done]
> [automatically because of the potential for mail loops. ]
> [If you do not include this Cc, your reply may be ig- ]
> [nored unless you are responding to an explicit request ]
> [from a developer. ]
> [Reply only with text; DO NOT SEND ATTACHMENTS! ]
>
>
> Synopsis: Incorrect assumptions in the 1.3.0 Configure script for Linux
> 2.0.x/libc5 (non-glibc2) systems.
>
> State-Changed-From-To: open-feedback
> State-Changed-By: rse
> State-Changed-When: Mon Aug 3 00:48:04 PDT 1998
> State-Changed-Why:
> I'm a little bit confused. Because first Apache built
> fine under Debian and RedHat boxes and the src/Configure
> script has correct entries to check for -ldl and -lcrypt
> IMHO. You say that it's unable to see that -ldl and
> -lcrypt is needed. When this is the case then
> the TestCompile stuff is broken for you. Can you
> try the two TestCompile command manually and see
> why they lead to incorrect results on your Linux box?
I've discovered that the TestCompile script on my box doesn't
like the "trap" line at the top. It seems that the TestCompile
script *always* exits with the status code of 1. This obviously
breaks the Configure script for me.
If I duplicate the body of the "trap" code and place it at the
bottom of the TestCompile script, things work correctly:
if AP_PPSEARCHPATH=`pwd` ./$AP_PRINTPATH -s $TARGET ; then
exstat=0
fi
rm -f Makefile dummy testfunc.c testfunc
exit $exstat
If I don't do this, when the script executes the body of the
trap command upon script exit, $exstat is always "1". I bet
my shell is replacing "exit $exstat" with "exit 1" as that's
what the value of $exstat is at the time the trap line
appears. (Whereas, it shouldn't be substituting at that
point). It sounds like this might just be a bug in my
/bin/sh (which is actually a link to /bin/bash).
Strange. Anyway, that's just another possible workaround,
but I should grab a newer version of bash and see if that
clears it up. But with my current bash, I need to stick
the rm/exit lines at the bottom of TestCompile to have it
work properly.
-Dossy
--
URL: http://www.panoptic.com/~dossy -< BORK BORK! >- E-MAIL: [EMAIL PROTECTED]
Now I'm who I want to be, where I want to be, doing what I've always said I
would and yet I feel I haven't won at all... (Aug 9, 95: Goodbye, JG.)
"You should change your .sig; not that the world revolves around me." -s. sadie
