gedit-2.24.2 doesn't build because of the damn libtool problem, as of many other ebuilds (there are a few bug reports around here, moreover I just fixed fftw-3.2 ebuild and I suspect there are many other I'll have to fix during this 'emerge -u world'). I'm in ~amd64. I am going to attach a working ebuild.
Steps to Reproduce:
1. emerge gedit
Created attachment 173347 [details]
Working gedit-2.24.2 ebuild
This ebuild works as expected
please don't complain about using ~arch ebuild on a arch system kthxbye
err sorry, misread.
Please post emerge --info and build.log. I have ~amd64 and it built just fine when I bumped it.
Also please post patch against ebuilds not full ebuilds.
I'm having the very same problem of the OP, although I'm on ~x86. I'll attach emerge --info and build.log shortly.
I can confirm that, using the updated ebuild provided in this bug, gedit compiles perfectly.
Created attachment 173529 [details]
Created attachment 173530 [details]
build.log from failed compilation
I eventually had to download the sources to figure it out
(I really hate to do it), but the problem is actually quite simple.
gedit was makedist'd with libtool 2.
Now, the problem hits only <libtool-2 systems.
For <libtool-2, AC_CONFIG_MACRO_DIR had no meaning,
so the libtool macro went straight to aclocal.m4.
For libtool-2 series, that macro is a hint for libtoolize
where to put libtool macro, so in this case, libtool macros went into
When libtoolize was run on a <libtool-2 system, ltmain.sh script
was overwritten, but the macros in m4/ dir were untouched.
The effect: conflict between new macros and old script.
So the fix: 'rm m4/lt* m4/libtool.m4' is indeed the correct one.
thanks for the description, that what led to the rewrite of the summary already. Please consider we are just missing time to fix this issue and this is why it's still open.
oh and btw guys, you should switch to libtool-2 it's way better than 1 and it would have avoided you this pain :p
(In reply to comment #9)
> oh and btw guys, you should switch to libtool-2 it's way better than 1 and it
> would have avoided you this pain :p
No way. The only reason to upgrade a tool such as libtool is that you miss some important feature which blocks the build process. This is not really the case.
So I guess this bug explains why this kicked in now; somewhere between gedit 2.24.1 and 2.24.2, I was required to upgrade libtool from 1.5* to 2.2* in order to be able to build it.
This was most distressing.
I've upgraded libtool now, and been through the `emerge -1 @preserved-rebuild` cycle which, mercifully, was only 7 packages or so. Hooray for Portage 2.2.
fixed without a bump, thanks for reporting.