On Tue, Feb 26, 2013 at 05:17:08PM +0100, Matthias Klose wrote:
> this works when setting CFLAGS to -O0:
>
> include /usr/share/dpkg/buildflags.mk
> CFLAGS := $(subst -O2,-O0,$(CFLAGS))
> export CFLAGS
>
> -Og works too for GCC 4.8.
I will look into this as soon as I have a bit of spare time and a gcc-4.8
setup ready.
> but given all the ignored warnings, this rather smells like buggy code.
Most of PDL's C code is autogenerated, resulting into (superfluous) declartions
of then unused variables, which lead to most of the warnings in the build
process.
> maybe not related, but pdl.PL looks wrong too ...
yep, this is clearly an out-of-bounds access. Thanks for reporting :)
the 'pdl' wrapper itself is not widely used; basically, it is just there so a
user can directly use 'pdl' as an interpreter for a script. Most people I
know use /usr/bin/perl and load PDL via 'use' into perl, leading to this
issue not having come up in the past.
> main(int argc, char **argv) {
> char perldl[BUFSIZ];
> int pipes[2];
>
> [...]
> if(pid==0) {
> dup2(pipes[1],1);
> dup2(pipes[2],2);
--
c u
henning
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
