Thank you for reply so soon! Is "PERL=..." for "./configure" only? I exec `PERL=<path to perl 5.10> perl -V`, and it still show old 5.6 ( but PATH=<path to per 5.10 dir>:$PATH perl -V` show 5.10... )
Removing perl did not work, as you said, because of the #!/usr/bin/perl header, and also some hardcoded search path between autotools components. I will try to do some more experiments... thanks :-) sincerely, Mat. 2010/6/21 Patrick von Reth <[email protected]>: > Hi I found ways to override perl (set PERL= ...) for configure but the perl > scripts in autotools are started over sh and the #!/usr/bin/perl ,removing > perl from the msys installation will only result in an unusable autotools. > > On 21 June 2010 15:17, Mat <[email protected]> wrote: >> >> Hi, >> >> Thank you for your works!! >> The feature is great, I have tested it, and it did call the autogen.sh >> scripts in msys execuation. >> >> The autogen.sh passed first some steps, but did not pass all routines, >> stoped at the same problem. >> "Can't locate threads.pm in @INC..." >> ( as the same problem I mentioned last reply with screenshot ) >> >> After tracing the problem in these days, I found some points, and share >> below: >> >> * use "export PERL5LIB=<path to perl libs *.pm> " in shell could set >> the perl search path without change code >> * I found msys installation contains "perl 5.6" which has no >> "threads.pm" .. and other new files that required by new tools. >> * I have dev-util/perl 5.10 installed via emerge, but haven't found >> ways to override the msys perl 5.6. ( maybe the simplest way is to >> delete the 5.6 files? ) >> >> >> The new improved autotools package is more convenient, it did helps, >> thank you very much!! >> >> sincerely, Mat. >> >> >> 2010/6/19 Patrick von Reth <[email protected]>: >> > Hi, >> > yesterday I added a autotools bootsrap support, so if you set >> > "self.subinfo.options.configure.bootstrap = True" in a autotools emerge >> > package, emerge will run autogen.sh before configure. >> > Theoretically its now possible to add autotools git repos. >> > Patrick >> > >> > On 10 June 2010 08:44, Patrick von Reth <[email protected]> wrote: >> >> >> >> Hm probably the bast way would be using tarballs like we did before, >> >> autotools are a very very bad thing on Windows >> >> Patrick >> >> >> >> 2010/6/10 Mat <[email protected]> >> >>> >> >>> Hi, I just tried to change path to /opt/autotools, it does pass the >> >>> prefix search path, thanks :-) >> >>> >> >>> And I encounter another problem, that "threads.pm" is not found in >> >>> @INC >> >>> pathes. >> >>> ( as attachment shows ) >> >>> >> >>> I am strange to perl related settings, would you have any >> >>> idea/suggestion about this? >> >>> >> >>> sincerely, Mat. >> >>> >> >>> 2010/6/10 Patrick von Reth <[email protected]>: >> >>> > Ok so autotools should be plcaed at /opt/autotools/bin I could >> >>> > change >> >>> > that >> >>> > easily >> >>> > >> >>> > On 9 June 2010 17:58, Mat <[email protected]> wrote: >> >>> >> >> >>> >> Hi, >> >>> >> >> >>> >> "testing/autotools" can be emerge/unmerge successfully, thanks. >> >>> >> >> >>> >> I found some problem at run-time, and write feedback as below: >> >>> >> >> >>> >> 1. the path in the wrapper script ( /bin/autoconf, >> >>> >> /bin/automake,...) >> >>> >> are not matched. >> >>> >> Original => LOCATION="/opt/autotools/bin" >> >>> >> It can run successfully after I change it >> >>> >> After => LOCATION="/bin" >> >>> >> >> >>> >> 2. There is some missing perl include path ( as screenshot display >> >>> >> ) >> >>> >> >> >>> >> 3. libtool is missing. libtool is usually required by libraries >> >>> >> packages. >> >>> >> >> >>> >> Any idea/suggstion? many thanks.. >> >>> >> >> >>> >> sincerely, Mat. >> >>> >> >> >>> >> On Wed, Jun 9, 2010 at 7:12 PM, Mat <[email protected]> wrote: >> >>> >> > Great job, thank you! >> >>> >> > >> >>> >> > I am going to try it and would like to feedback if there is >> >>> >> > something >> >>> >> > helpful :-) >> >>> >> > >> >>> >> > 2010/6/9 Patrick von Reth <[email protected]>: >> >>> >> >> Hi Mat, >> >>> >> >> I switched our msys source and added also a autotools package, >> >>> >> >> with >> >>> >> >> the >> >>> >> >> new >> >>> >> >> msys we also ship a msys-perl which as far as I know is needed >> >>> >> >> for >> >>> >> >> autotools(hardcoded path) I also fixed the problem which ocures >> >>> >> >> with >> >>> >> >> normal >> >>> >> >> configure if msys-perl is installed. >> >>> >> >> Maybe we also can add the direct autotools support to emerge. >> >>> >> >> But for what is the pkg-config-dev package needed? >> >>> >> > dbus-c++'s configure.ac use 'PKG_CHECK_MODULES' macro to invoke >> >>> >> > pkg-config check function, some functions/macro is defined in >> >>> >> > 'pkg-config.m4', which are in pkg-config-dev package. >> >>> >> > >> >>> >> >> Regards >> >>> >> >> Patrick >> >>> >> >> >> >>> >> >> 2010/6/4 Mat <[email protected]> >> >>> >> >>> >> >>> >> >>> Hi All, >> >>> >> >>> >> >>> >> >>> I tried to made a package for autotools toolchain [1][2]. >> >>> >> >>> The package now can run and generates "./configure" form >> >>> >> >>> compact >> >>> >> >>> autotool-based source. >> >>> >> >>> It is still experimental, and hope it helps. >> >>> >> >>> >> >>> >> >>> sincerely, Mat. >> >>> >> >>> >> >>> >> >>> [1]. attachment://autotools.patch >> >>> >> >>> [2]. attachment://pkg-config.patch >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> >> >>> Kde-windows mailing list >> >>> >> >>> [email protected] >> >>> >> >>> https://mail.kde.org/mailman/listinfo/kde-windows >> >>> >> >>> >> >>> >> >> >> >>> >> >> >> >>> >> >> _______________________________________________ >> >>> >> >> Kde-windows mailing list >> >>> >> >> [email protected] >> >>> >> >> https://mail.kde.org/mailman/listinfo/kde-windows >> >>> >> >> >> >>> >> >> >> >>> >> > >> >>> >> _______________________________________________ >> >>> >> Kde-windows mailing list >> >>> >> [email protected] >> >>> >> https://mail.kde.org/mailman/listinfo/kde-windows >> >>> > >> >>> > >> >>> > _______________________________________________ >> >>> > Kde-windows mailing list >> >>> > [email protected] >> >>> > https://mail.kde.org/mailman/listinfo/kde-windows >> >>> > >> >>> > >> >>> >> >>> _______________________________________________ >> >>> Kde-windows mailing list >> >>> [email protected] >> >>> https://mail.kde.org/mailman/listinfo/kde-windows >> >>> >> >> >> > >> > >> > _______________________________________________ >> > Kde-windows mailing list >> > [email protected] >> > https://mail.kde.org/mailman/listinfo/kde-windows >> > >> > >> _______________________________________________ >> Kde-windows mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/kde-windows > > > _______________________________________________ > Kde-windows mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-windows > > _______________________________________________ Kde-windows mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-windows
