LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   MESA / Automake / aclocal version problem on Slack 14.0 and current... (https://www.linuxquestions.org/questions/slackware-14/mesa-automake-aclocal-version-problem-on-slack-14-0-and-current-4175479416/)

NoStressHQ 10-03-2013 01:59 AM
MESA / Automake / aclocal version problem on Slack 14.0 and current...
 
Hi, got a "little" problem.

I need to build a fresh MESA, and sadly it requires new versions of automake and aclocal (at least)...

And even on Slackware-current, the versions provided are "behind" the one expected by Mesa (Mesa 9.2.0).

Mesa requires:
- automake 1.12 (Slackware current provides 1.11.5)
- aclocal 1.12 (Slackware 14 provides 1.11.5)

If I don't miss anything, anyway both tools are in the automake package so that's why both versions are coupled...

(I don't have -current installed so I just watched the PACKAGES.TXT).

Anyway, could be they be upgraded for -current ?

And meanwhile does anybody have any tip so I can get around with MESA build ? Is it safe to make an update myself ? Just need to change the archive version in the stock SlackBuild ?

Sorry I can't try that right now, it's 9am and I need to go to sleep ;). So if someone have already done that and give me some hints/warnings that would be great.

Thanks!

Cheers

Garry.

gnashley 10-03-2013 02:14 AM
You can upgrade those without much trouble -there could be sources which might not easily compile because of having too *new* a version, but unless you are re-compiling lots of the original sources you shouldn't have any problems. Just be sure to use the SlackBuild, with modified versions, to build the package.

NoStressHQ 10-03-2013 02:26 AM
Alright, thanks gnashley. I usually never recompile vanilla Slackware packages, I trust Mr Volkerding :).

I only compile some libraries for my own development purposes in a "sandbox" tree. I hope it won't break the "extra builds" from SBO and such...

Thanks again.

NoStressHQ 10-03-2013 09:32 AM
After a good sleep, I think I'd rather build them in a isolated directory, and override the path "locally" in my build environment...

This way I won't mess up the system wide tools, and will reduce the pain if something changed drastically.

Sleeping is wise ;)

PS/ Anyway, any plan to upgrade this package for Slackware-current (14.1?)

NoStressHQ 10-03-2013 12:13 PM
This is weird...

I built latest versions of automake (and autoconf while I was a it), and installed them in a isolated directory branch.

I override the PATH prefixing it with my isolated 'bin' directory, so in this "environment" the first tools should be from my isolation bin. And it works when trying it on the CLI.

But when I run the MESA configure, it still complains it's not the right version.

That time I got a newer version (1.14 instead of the 1.11.5 from Slackware AND the 1.12 expected by Mesa)...

So does mesa check/expect the exact 1.12 version ? Or something else happen ?

Does anybody have succeeded in building the last Mesa release (9.2.0) ?

Thanks.

Garry.

Edit: Just tried trying to compile 1.12(.6) and then it doesn't complain anymore... Well that's a MESA problem, I'll report to them. This is so stupid to check for an "exact" match, unless they use very specific features, which I heavily doubt of.

NoStressHQ 10-03-2013 12:37 PM
Anyway, even after that, building Mesa is a real PITA... Don't know since which version, it's been a while I haven't built it but this version is crap as hell. Now it complains about LIBTOOL...

While it was ok to rebuild automake, even pkg-tool, now it starts to get a mess.

So I'm still accepting tips if anyone have some experience in building it on Slackware.

Richard Cranium 10-09-2013 09:05 AM
Did you try building via scons?

jon lee 10-09-2013 09:19 AM
I don't remember having to update those for Mesa, but I may have at an earlier period for something else. I do know that an update of llvm is required if you want the radeon r600 module, and when you compile it you have to enable "experimental targets" in llvm to get it.

Also the latest Mesa breaks Intel DRI drivers for Mixxx and some games ran from Wine :(
(forcing one to use gallium drivers which don't perform nearly as well)

Edit:
Up to 9.2.1 here, but if you're on Intel, I would stick with 9.1.6 (or whatever) for awhile.
http://i102.photobucket.com/albums/m...psfd068bc2.png

I dunno...
Code:
bash-4.2$ automake --version
automake (GNU automake) 1.11.5
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey <tromey@redhat.com>
      and Alexandre Duret-Lutz <adl@gnu.org>.
How are you getting it (the Mesa archive), that might be the problem.

Edit: Oh, I see... you have to do a ./autogen.sh first which will take care of it.

mats_b_tegner 10-09-2013 03:27 PM
I'm able to build mesa 9.2.1 using the SlackBuild-script from /source/x/mesa on slackware64-current with automake 1.13.4. I used automake 1.14 for a while but transmission 2.82 required automake 1.13 so I downgraded to automake 1.13.4 and that version seems to work with mesa as well.

Mats

jlpoole 12-28-2014 06:51 AM
Quote:
Originally Posted by NoStressHQ (Post 5039421)
This is weird...

...

I override the PATH prefixing it with my isolated 'bin' directory, so in this "environment" the first tools should be from my isolation bin. And it works when trying it on the CLI.
...
Automake-1.14 also relies on its accompanying Perl libraries, so you may need to make sure Automake's libraries are picked up using:
Code:
export PERL5LIB=[path to automake-1.14/lib]
For example, I built automake-1.14 under /usr/local/src.
Code:
        root@slack3:/usr/local/src/automake-1.14# export PATH=/usr/local/src/automake-1.14/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/kde4/libexec:/usr/lib64/qt/bin:/usr/share/texmf/bin
        root@slack3:/usr/local/src/automake-1.14# automake --version
        Can't locate Automake/Config.pm in @INC (you may need to install the Automake::Config module) (@INC contains: /usr/local/share/automake-1.14 /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/local/src/automake-1.14/bin/automake line 48.
        BEGIN failed--compilation aborted at /usr/local/src/automake-1.14/bin/automake line 48.
        root@slack3:/usr/local/src/automake-1.14# export PERL5LIB=/usr/local/src/automake-1.14/lib
        root@slack3:/usr/local/src/automake-1.14# automake --version
        automake (GNU automake) 1.14
        Copyright (C) 2013 Free Software Foundation, Inc.
        License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
        This is free software: you are free to change and redistribute it.
        There is NO WARRANTY, to the extent permitted by law.

        Written by Tom Tromey <tromey@redhat.com>
                  and Alexandre Duret-Lutz <adl@gnu.org>.
        root@slack3:/usr/local/src/automake-1.14#


All times are GMT -5. The time now is 09:07 AM.