It's probably this line in ext/Errno/Errno_pm.PL:

return unless defined $file and -f $file;

This script does an initial preprocessor run of errno.h, pulls out the
list of headers it brings in and then runs this list through 'gcc -dM
...' to get the errno values.  The list of headers from the initial run
is relative to the host so this check to see if it's reachable from the
target is probably failing.  You can either comment out this line or nfs
mount $QNX_TARGET/usr/include from the host at the same pount on the
target.

perl, sigh...

On Mon, Feb 09, 2015 at 09:23:38AM -0500, Aaron Gawlik wrote:
> I have followed the method for building pkgsrc on QNX6.6 from the link below and am able to bootstrap and bmake 
lighttpd with its dependencies. Arch is x86, host is Ubuntu VM, target is x86 QNX6.6 VM.
> http://community.qnx.com/sf/wiki/do/viewPage/projects.pkgsrc/wiki/PkgsrcOnQnx6.6
> 
> Several packages require perl and attempt to build perl-5.18.0nb2. Regardless of -64bit* and -threads options it fails
 with the message below. Even commenting out the "die" line, the build fails at a following stage.
> -------------------------------------------------
> Running Makefile.PL in ext/Errno
> ../../miniperl -I../../lib Makefile.PL INSTALLDIRS=perl INSTALLMAN1DIR=none INSTALLMAN3DIR=none PERL_CORE=1 LIBPERL_A=
libperl.so
> Writing Makefile for Errno
> Making all in ext/Errno
>  /usr/pkg/bin/bmake all PERL_CORE=1 LIBPERL_A=libperl.so
> ../../miniperl "-I../../lib" "-I../../lib" Errno_pm.PL Errno.pm
> No error definitions found at Errno_pm.PL line 204.
> *** Error code 2
> 
> Stop.
> bmake: stopped in /home/ubuntu/pkgsrc/lang/perl5/work/perl-5.18.0/ext/Errno
> Unsuccessful make(ext/Errno): code=256 at make_ext.pl line 490.
> *** Error code 89
> 
> Stop.
> bmake: stopped in /home/ubuntu/pkgsrc/lang/perl5/work/perl-5.18.0
> *** Error code 1
> 
> Stop.
> bmake: stopped in /home/ubuntu/pkgsrc/lang/perl5
> *** Error code 1
> 
> Stop.
> bmake: stopped in /home/ubuntu/pkgsrc/lang/perl5
> -------------------------------------------------
> 
> From what I have found searching, there are sometimes issues with the errno.h path being hardcoded.  The path is 
defined as (line 139 in Errno.pm.PL):
> 	# Some Linuxes have weird errno.hs which generate
> 	# no #file or #line directives
> 	my $linux_errno_h = -e '/usr/include/errno.h' ?
> 	    '/usr/include/errno.h' : '/usr/local/include/errno.h';
> 
> I've confirmed that errhno.h exists on the target machine via nfs mount from ${QNX_TARGET}/usr/include at /usr/include
/*.  Is there an issue that the gcc tools are actually on the host machine and accessed via ssh?  Should the host path 
be used?  Thank you for any help.
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post113268
> To cancel your subscription to this discussion, please e-mail general-pkgsrc-unsubscribe@community.qnx.com