Hi,<div>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.</div><div>Theoretically its now possible to add autotools git repos.</div>
<div><br></div><div>Patrick<br><br><div class="gmail_quote">On 10 June 2010 08:44, Patrick von Reth <span dir="ltr"><<a href="mailto:patrick@von-reth.de">patrick@von-reth.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hm probably the bast way would be using tarballs like we did before, autotools are a very very bad thing on Windows<div><br></div><div>Patrick<br><br><div class="gmail_quote">2010/6/10 Mat <span dir="ltr"><<a href="mailto:matlinuxer2@gmail.com" target="_blank">matlinuxer2@gmail.com</a>></span><div>
<div></div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, I just tried to change path to /opt/autotools, it does pass the<br>
prefix search path, thanks :-)<br>
<br>
And I encounter another problem, that "<a href="http://threads.pm" target="_blank">threads.pm</a>" is not found in @INC pathes.<br>
( as attachment shows )<br>
<br>
I am strange to perl related settings, would you have any<br>
idea/suggestion about this?<br>
<br>
sincerely, Mat.<br>
<br>
2010/6/10 Patrick von Reth <<a href="mailto:patrick@von-reth.de" target="_blank">patrick@von-reth.de</a>>:<br>
<div><div></div><div>> Ok so autotools should be plcaed at /opt/autotools/bin I could change that<br>
> easily<br>
><br>
> On 9 June 2010 17:58, Mat <<a href="mailto:matlinuxer2@gmail.com" target="_blank">matlinuxer2@gmail.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> "testing/autotools" can be emerge/unmerge successfully, thanks.<br>
>><br>
>> I found some problem at run-time, and write feedback as below:<br>
>><br>
>> 1. the path in the wrapper script ( /bin/autoconf, /bin/automake,...)<br>
>> are not matched.<br>
>> Original => LOCATION="/opt/autotools/bin"<br>
>> It can run successfully after I change it<br>
>> After => LOCATION="/bin"<br>
>><br>
>> 2. There is some missing perl include path ( as screenshot display )<br>
>><br>
>> 3. libtool is missing. libtool is usually required by libraries packages.<br>
>><br>
>> Any idea/suggstion? many thanks..<br>
>><br>
>> sincerely, Mat.<br>
>><br>
>> On Wed, Jun 9, 2010 at 7:12 PM, Mat <<a href="mailto:matlinuxer2@gmail.com" target="_blank">matlinuxer2@gmail.com</a>> wrote:<br>
>> > Great job, thank you!<br>
>> ><br>
>> > I am going to try it and would like to feedback if there is something<br>
>> > helpful :-)<br>
>> ><br>
>> > 2010/6/9 Patrick von Reth <<a href="mailto:patrick.vonreth@gmail.com" target="_blank">patrick.vonreth@gmail.com</a>>:<br>
>> >> Hi Mat,<br>
>> >> I switched our msys source and added also a autotools package, with the<br>
>> >> new<br>
>> >> msys we also ship a msys-perl which as far as I know is needed for<br>
>> >> autotools(hardcoded path) I also fixed the problem which ocures with<br>
>> >> normal<br>
>> >> configure if msys-perl is installed.<br>
>> >> Maybe we also can add the direct autotools support to emerge.<br>
>> >> But for what is the pkg-config-dev package needed?<br>
>> > dbus-c++'s <a href="http://configure.ac" target="_blank">configure.ac</a> use 'PKG_CHECK_MODULES' macro to invoke<br>
>> > pkg-config check function, some functions/macro is defined in<br>
>> > 'pkg-config.m4', which are in pkg-config-dev package.<br>
>> ><br>
>> >> Regards<br>
>> >> Patrick<br>
>> >><br>
>> >> 2010/6/4 Mat <<a href="mailto:matlinuxer2@gmail.com" target="_blank">matlinuxer2@gmail.com</a>><br>
>> >>><br>
>> >>> Hi All,<br>
>> >>><br>
>> >>> I tried to made a package for autotools toolchain [1][2].<br>
>> >>> The package now can run and generates "./configure" form compact<br>
>> >>> autotool-based source.<br>
>> >>> It is still experimental, and hope it helps.<br>
>> >>><br>
>> >>> sincerely, Mat.<br>
>> >>><br>
>> >>> [1]. attachment://autotools.patch<br>
>> >>> [2]. attachment://pkg-config.patch<br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> Kde-windows mailing list<br>
>> >>> <a href="mailto:Kde-windows@kde.org" target="_blank">Kde-windows@kde.org</a><br>
>> >>> <a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
>> >>><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Kde-windows mailing list<br>
>> >> <a href="mailto:Kde-windows@kde.org" target="_blank">Kde-windows@kde.org</a><br>
>> >> <a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
>> >><br>
>> >><br>
>> ><br>
>> _______________________________________________<br>
>> Kde-windows mailing list<br>
>> <a href="mailto:Kde-windows@kde.org" target="_blank">Kde-windows@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
><br>
><br>
> _______________________________________________<br>
> Kde-windows mailing list<br>
> <a href="mailto:Kde-windows@kde.org" target="_blank">Kde-windows@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
><br>
><br>
</div></div><br>_______________________________________________<br>
Kde-windows mailing list<br>
<a href="mailto:Kde-windows@kde.org" target="_blank">Kde-windows@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
<br></blockquote></div></div></div><br></div>
</blockquote></div><br></div>