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

Re: Perl IPC::Open3 bug, affects apt-get, compiler issue?



On Mon, Jun 17, 2002 at 02:01:36PM -0700, Tony Lindgren wrote:
> * Nicholas Clark <nick@unfortu.net> [020617 13:32]:

> No differences in compile flags for perl and debug-perl, except:
> 
> nw:~# perl -V > perl.txt
> nw:~# debugperl -V > debugperl.txt
> nw:~# diff -u perl.txt debugperl.txt 
> --- perl.txt    Mon Jun 17 13:47:29 2002
> +++ debugperl.txt       Mon Jun 17 13:47:38 2002
> @@ -28,9 +28,9 @@
>  
>  
>  Characteristics of this binary (from libperl): 
> -  Compile-time options: USE_LARGE_FILES
> +  Compile-time options: DEBUGGING USE_LARGE_FILES
>    Built under linux
> -  Compiled at Jan 17 2002 09:02:54
> +  Compiled at Jan 17 2002 09:45:34
>    @INC:
>      /usr/local/lib/perl/5.6.1
>      /usr/local/share/perl/5.6.1
> 
> But maybe -DDEBUGGING includes -g?

perl -V output does have compile flags in it:

  Compiler:
    cc='cc', ccflags ='-DDEBIAN -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
    optimize='-O1',

-g shows up as
     optimize='-g',

so if debugperl and perl differed in optimisation I would have expected your
diff to show it up.

The perl Configure script will add -DDEBUGGING into the compiler flags for
you if you answer -g to its question about which optimiser flag to use, but
that's only logic about which default answers to prompt with at configure
time. It's quite possible to set -O, -g and -DDEBUGGING completely
independently of each other.

Does anyone know if the author of FastFPE yet knows about the problem?
[Better still, is there a solution?] I guess it's not that nice to report
at the moment as the test case is rather large and ambiguous.

Nicholas Clark
-- 
Even better than the real thing:	http://nms-cgi.sourceforge.net/


-- 
To UNSUBSCRIBE, email to debian-arm-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: