Skip Menu |

This queue is for tickets about the Filesys-Statvfs_Statfs_Df CPAN distribution.

Report information
The Basics
Id: 19275
Status: open
Priority: 0/
Queue: Filesys-Statvfs_Statfs_Df
People
Owner: Nobody in particular
Requestors: jeffb [...] uchicago.edu
Cc:
AdminCc:
Bug Information
Severity: Critical
Broken in: 0.75
Fixed in: (no value)

History Show all quoted text
  Mon May 15 14:56:52 2006 Guest - Ticket created
Subject: Cannot install Filesys-Statvfs_Statfs_Def
I have OpenBSD 3.9 and want to install Filesys-Statvfs_Statfs_Df 0.75 First, a few things: mail:~ # uname -a OpenBSD mail 3.9 GENERIC#1 i386 mail:~ # perl -v This is perl, v5.8.6 built for i386-openbsd ======== report ========== This build does not have statfs.h. The build seems to recognize that it is in mount.h, but still can't find it. .cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # perl Makefile.PL It looks like you are on a Darwin or BSD system. Since I could not find a statfs or statvfs header, I will assume you use the mount.h and param.h headers and statfs() Checking if your kit is complete... Looks good Writing Makefile for Filesys::Statfs mail:~/.cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # make cp Df.pm blib/lib/Filesys/Df.pm cp Statvfs.pm blib/lib/Filesys/Statvfs.pm cp Statfs.pm blib/lib/Filesys/Statfs.pm /usr/bin/perl /usr/libdata/perl5/ExtUtils/xsubpp -typemap /usr/libdata/perl5/ExtUtils/typemap -typemap typemap Statfs.xs > Statfs.xsc && mv Statfs.xsc Statfs.c Please specify prototyping behavior for Statfs.xs (see perlxs manual) cc -c -fno-strict-aliasing -fno-delete-null-pointer-checks -pipe -I/usr/local/include -O2 -DVERSION=\"0.75\" -DXS_VERSION=\"0.75\" -DPIC -fPIC "-I/usr/libdata/perl5/i386-openbsd/5.8.6/CORE" Statfs.c Statfs.xs:14:24: sys/statfs.h: No such file or directory Statfs.xs: In function `XS_Filesys__Statfs_statfs': Statfs.xs:39: error: storage size of `st' isn't known *** Error code 1 I tried fooling it by making a symlink to mount.h but /.cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # perl Makefile.PL /usr/include/sys/statvfs.h does not exist, but /usr/include/sys/statfs.h exists. Using statfs() with Df.pm Checking if your kit is complete... Looks good Writing Makefile for Filesys::Statfs mail:~/.cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # make cp Df.pm blib/lib/Filesys/Df.pm cp Statvfs.pm blib/lib/Filesys/Statvfs.pm cp Statfs.pm blib/lib/Filesys/Statfs.pm /usr/bin/perl /usr/libdata/perl5/ExtUtils/xsubpp -typemap /usr/libdata/perl5/ExtUtils/typemap -typemap typemap Statfs.xs > Statfs.xsc && mv Statfs.xsc Statfs.c Please specify prototyping behavior for Statfs.xs (see perlxs manual) cc -c -fno-strict-aliasing -fno-delete-null-pointer-checks -pipe -I/usr/local/include -O2 -DVERSION=\"0.75\" -DXS_VERSION=\"0.75\" -DPIC -fPIC "-I/usr/libdata/perl5/i386-openbsd/5.8.6/CORE" Statfs.c Statfs.xs: In function `XS_Filesys__Statfs_statfs': Statfs.xs:58: error: structure has no member named `f_type' Statfs.xs:59: error: structure has no member named `f_type' Statfs.xs:61: error: structure has no member named `f_type' *** Error code 1 Jeff
  Mon May 15 15:22:33 2006 Guest - Correspondence added
From: Ian Guthrie
On Mon May 15 14:56:52 2006, guest wrote: Show quoted text
> I have OpenBSD 3.9 and want to install Filesys-Statvfs_Statfs_Df 0.75 > > First, a few things: > mail:~ # uname -a > OpenBSD mail 3.9 GENERIC#1 i386 > mail:~ # perl -v > This is perl, v5.8.6 built for i386-openbsd > > ======== report ========== > This build does not have statfs.h. The build seems to recognize that it > is in mount.h, but still can't find it. > > > .cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # perl Makefile.PL > > It looks like you are on a Darwin or BSD system. > > Since I could not find a statfs or statvfs header, > > I will assume you use the mount.h and param.h headers > > and statfs() > > Checking if your kit is complete... > > Looks good > > Writing Makefile for Filesys::Statfs > > mail:~/.cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # make > > cp Df.pm blib/lib/Filesys/Df.pm > > cp Statvfs.pm blib/lib/Filesys/Statvfs.pm > > cp Statfs.pm blib/lib/Filesys/Statfs.pm > > /usr/bin/perl /usr/libdata/perl5/ExtUtils/xsubpp -typemap > /usr/libdata/perl5/ExtUtils/typemap -typemap typemap Statfs.xs > > Statfs.xsc && mv Statfs.xsc Statfs.c > > Please specify prototyping behavior for Statfs.xs (see perlxs manual) > > cc -c -fno-strict-aliasing -fno-delete-null-pointer-checks -pipe > -I/usr/local/include -O2 -DVERSION=\"0.75\" -DXS_VERSION=\"0.75\" > -DPIC -fPIC "-I/usr/libdata/perl5/i386-openbsd/5.8.6/CORE" Statfs.c > > Statfs.xs:14:24: sys/statfs.h: No such file or directory > > Statfs.xs: In function `XS_Filesys__Statfs_statfs': > > Statfs.xs:39: error: storage size of `st' isn't known > > *** Error code 1 > > > > > > I tried fooling it by making a symlink to mount.h but > > > > /.cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # perl Makefile.PL > > > > /usr/include/sys/statvfs.h does not exist, > > but /usr/include/sys/statfs.h exists. > > Using statfs() with Df.pm > > Checking if your kit is complete... > > Looks good > > Writing Makefile for Filesys::Statfs > > mail:~/.cpan/build/Filesys-Statvfs_Statfs_Df-0.75 # make > > cp Df.pm blib/lib/Filesys/Df.pm > > cp Statvfs.pm blib/lib/Filesys/Statvfs.pm > > cp Statfs.pm blib/lib/Filesys/Statfs.pm > > /usr/bin/perl /usr/libdata/perl5/ExtUtils/xsubpp -typemap > /usr/libdata/perl5/ExtUtils/typemap -typemap typemap Statfs.xs > > Statfs.xsc && mv Statfs.xsc Statfs.c > > Please specify prototyping behavior for Statfs.xs (see perlxs manual) > > cc -c -fno-strict-aliasing -fno-delete-null-pointer-checks -pipe > -I/usr/local/include -O2 -DVERSION=\"0.75\" -DXS_VERSION=\"0.75\" > -DPIC -fPIC "-I/usr/libdata/perl5/i386-openbsd/5.8.6/CORE" Statfs.c > > Statfs.xs: In function `XS_Filesys__Statfs_statfs': > > Statfs.xs:58: error: structure has no member named `f_type' > > Statfs.xs:59: error: structure has no member named `f_type' > > Statfs.xs:61: error: structure has no member named `f_type' > > *** Error code 1 > > > Jeff > >
I think this has to do with a really lame bug in Makefile.PL. It looks like I was looking to see if the osname matched /bsd$/ to determine whether the system was BSD, but then when it came time to define what headers to use, I see if the osname equals "freebsd". If that part of the code is changed to match /^bsd|bsd$/i I think it will work. Anyway this problem should be fixed with the Filesys-Df-0.90 build which is in the module list and my CPAN directory. I would suggest upgrading to that to take care of the issue. I redid almost all the code with .90 and there are several bug fixes in it. I also just put out a Filesys-DfPortable version if you want the code to be portable between Windows an Unix. I have aldo scheduled the 0.75 version for deletion. Cheers, Ian
  Mon May 15 15:22:34 2006 The RT System itself - Status changed from 'new' to 'open'