[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
FreeBSD build failures and other requests
From: Vikas N Kumar ####@####.#### Date: 1 Dec 2014 19:21:41 -0000 Message-Id: <547CBFBB.7090006@vikaskumar.org> Hello I have been writing an open source Perl module called "Alien::gputils" (http://metacpan.org/pod/Alien::gputils) that will basically allow Perl-based build tools to automatically pick up the most recent gputils install or build the latest release if gputils has not been installed on the system. However, there are some serious failures on FreeBSD systems when the perl module downloads the tarball and starts building it. The commands used by the perl module to build on non-Windows systems are: $ ./configure --prefix=$PREFIX --disable-html-doc --without-mplabx-path $ make && make check However, there is a Yacc/Flex problem at which the failure to build occurs. Below is a link to an automated build report from FreeBSD. If you grep for "PROGRAM OUTPUT" you can see the progress of the build and it will end with "byacc" or "YFLAGS" errors. http://www.cpantesters.org/cpan/report/6065ed38-70db-11e4-bbd3-9658e0bfc7aa Please advise as to how to fix the build on *BSD systems. Also, since the Perl module will try to build the software on systems that may not have the appropriate Bison/Flex/Lex/Yacc software, is it possible to ship the correctly generated C files along with the "release tarball" so that if those files are present the user does not need to have Bison/Yacc/Flex on their systems. This will allow Perl to build a native Windows version as well. Otherwise installing Bison/Flex as dependencies gets difficult as they also do not build natively on Windows without serious effort. The reason this is necessary is to allow for module deployment. Thanks Vikas Kumar. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |