Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
libtool.m4 and ltmain.sh have a version mismatch!
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
pdl
n00b
n00b


Joined: 06 Apr 2006
Posts: 42

PostPosted: Sat Jul 19, 2008 7:11 am    Post subject: libtool.m4 and ltmain.sh have a version mismatch! Reply with quote

Emerging the latest upgrade for x11-libs/pixman-0.11.8 failed. The key reasons appear to be ...
Code:

*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.26, ltmain.sh = 1.5.24) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

make: *** [config.status] Error 1
 *
 * ERROR: x11-libs/pixman-0.11.8 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2975:  Called x-modular_src_compile
 *             environment, line 3760:  Called x-modular_src_make
 *             environment, line 3796:  Called die
 * The specific snippet of code:
 *       emake || die "emake failed"
 *  The die message:
 *   emake failed


Does anybody recognize this? Among those who recognize it, does anybody know how to solve it? ... Thanks!
Back to top
View user's profile Send private message
askoff
Tux's lil' helper
Tux's lil' helper


Joined: 15 Apr 2004
Posts: 77

PostPosted: Sat Jul 19, 2008 12:18 pm    Post subject: Reply with quote

I have exactly the same problem.

EDIT: I just took ~ keyword off from the package and now it doesn't try to emerge it anymore. So I guess the problem is fixed now.
Back to top
View user's profile Send private message
NEOxAKIRA
Guru
Guru


Joined: 20 May 2007
Posts: 302
Location: France

PostPosted: Sat Jul 19, 2008 12:36 pm    Post subject: Reply with quote

I also have this problem, and i don't find how to emerge x11-libs/pixman-0.11.8 corectly...
so I emerged the last stable version of pixman which is x11-libs/pixman-0.10.0 and it's work fine for the moment.

If you succed in emerging x11-libs/pixman-0.11.8 just tell me how you do it, thanks

PS:
Sorry for my english, I'm french
Back to top
View user's profile Send private message
DuF
Advocate
Advocate


Joined: 09 Dec 2002
Posts: 2687
Location: Paris

PostPosted: Sat Jul 19, 2008 3:12 pm    Post subject: Reply with quote

Same here for me, it seems that there is a problem in the source because of the following message :
Code:
configure: error:

*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.22, ltmain.sh = 1.5.24) ***

Please run:

  libtoolize --copy --force



But for me it's not possible to perform the libtoolize --copy --force by using ebuild without changing it.
Back to top
View user's profile Send private message
blk_jack
Apprentice
Apprentice


Joined: 10 May 2002
Posts: 298
Location: Toronto

PostPosted: Sat Jul 19, 2008 7:21 pm    Post subject: Reply with quote

Same issue with me, except I'm getting it with all versions of pixman, not just the ~x86 masked one.

This all comes as a result of updating python, running python-updater and pixman being one of the packages it needs to compile along with over 100 others.

Any ideas?
Back to top
View user's profile Send private message
jmartos
Tux's lil' helper
Tux's lil' helper


Joined: 23 Mar 2008
Posts: 76

PostPosted: Sat Jul 19, 2008 8:02 pm    Post subject: Reply with quote

I had the same issue as blk_jack, but mine worked when I changed pixman to the stable non ~x86.
Back to top
View user's profile Send private message
0000000000000
Apprentice
Apprentice


Joined: 21 Mar 2008
Posts: 163

PostPosted: Sun Jul 20, 2008 7:46 am    Post subject: Reply with quote

i cannot emerge pixman after a python update either

i get a different error though:
Code:
checking whether to use SSE intrinsics... no
checking whether to use SSE2 intrinsics... no
configure: error: SSE2 intrinsics not detected


then it fails.
Back to top
View user's profile Send private message
pappy_mcfae
Watchman
Watchman


Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.

PostPosted: Sun Jul 20, 2008 8:56 am    Post subject: Reply with quote

Put me down for this one as well.
Code:
checking for objdir... .libs
checking for i486-pc-linux-gnu-ar... i486-pc-linux-gnu-ar
checking for i486-pc-linux-gnu-ranlib... i486-pc-linux-gnu-ranlib
checking for i486-pc-linux-gnu-strip... i486-pc-linux-gnu-strip
checking for correct ltmain.sh version... no
configure: error:

*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.26, ltmain.sh = 1.5.24) ***


The weird thing is it compiled once. Now it won't.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.
Back to top
View user's profile Send private message
johnfredcee
n00b
n00b


Joined: 31 Dec 2005
Posts: 10

PostPosted: Sun Jul 20, 2008 9:48 am    Post subject: Reply with quote

0000000000000 wrote:
i cannot emerge pixman after a python update either

i get a different error though:
Code:
checking whether to use SSE intrinsics... no
checking whether to use SSE2 intrinsics... no
configure: error: SSE2 intrinsics not detected


then it fails.


This is what I got, then I re-emerged it with -sse -sse2. Then I got the libtoolize message, then I removed the ~x86 keyword and then..it compiled. Well, ~x86 is supposed to be bleeding edge, so I guess I can't complain if things blow up from time to time while using it.

It does look like the ebuild or something needs some attention though.
Back to top
View user's profile Send private message
pappy_mcfae
Watchman
Watchman


Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.

PostPosted: Mon Jul 21, 2008 8:51 am    Post subject: Reply with quote

The sanity check error has been fixed in portage. Sync your tree and emerge pixman.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.
Back to top
View user's profile Send private message
desultory
Bodhisattva
Bodhisattva


Joined: 04 Nov 2005
Posts: 9410

PostPosted: Mon Jul 21, 2008 8:56 am    Post subject: Reply with quote

According to what appears to be the most relevant bug report, this has been fixed. If not please comment on the bug, including error messages and the full output of emerge --info there.
Back to top
View user's profile Send private message
jmartos
Tux's lil' helper
Tux's lil' helper


Joined: 23 Mar 2008
Posts: 76

PostPosted: Mon Jul 21, 2008 9:48 am    Post subject: Reply with quote

I can confirm that pixman-0.11.8 now compiles where it wasn't before. How about for everyone else with the problem?
Back to top
View user's profile Send private message
Timbers2k
Apprentice
Apprentice


Joined: 03 Oct 2003
Posts: 215

PostPosted: Mon Jul 21, 2008 1:32 pm    Post subject: Reply with quote

The only way I can get it to work is to add -sse2 to package.use. I'm on amd64 and the processor supports sse2.
Back to top
View user's profile Send private message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Mon Jul 21, 2008 10:06 pm    Post subject: Reply with quote

With a freshly synced portage tree, pixman-0.11.8 should now compile, and not give any libtool errors. If you have enabled the sse2 useflag, you need to use >=gcc-4.2, and it should give you an error message when you don't have that.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
pdl
n00b
n00b


Joined: 06 Apr 2006
Posts: 42

PostPosted: Wed Jul 23, 2008 6:25 am    Post subject: It's Fixed! Reply with quote

Now pixman 0.11.8 compiles properly for me. Thanks to whoever sorted this out.
Back to top
View user's profile Send private message
pappy_mcfae
Watchman
Watchman


Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.

PostPosted: Wed Jul 23, 2008 6:31 am    Post subject: Reply with quote

I wish I could take credit for that, but by the time I reported the bug, it had been fixed in portage. So, I also thank whoever fixed that bug even before it was reported as a bug.

Blessed be!
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum