Hi all
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
Those files are not installed anymore with latest pango. Is there a fix or is pango with meson/ninja not supported?
Kind regards Tim
On 11/24/2017 10:46 PM, Tim Tassonis wrote:
Hi all
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
Those files are not installed anymore with latest pango. Is there a fix or is pango with meson/ninja not supported?
I can now confirm that just by copying the pango .la files from an old installation using libtool will fix the issue and geany-plugins 1.32 the compiles fine against pango 1.40.14 using meson/ninja.
So, maybe geany-plugins should check about the existence of the pango la files, as it seems that pango in the future will drop autotools/libtool support (it's the gnome/redhat way).
Hey Tim,
Le 24/11/2017 à 13:46, Tim Tassonis a écrit :
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
Those files are not installed anymore with latest pango. Is there a fix or is pango with meson/ninja not supported?
I don't think .la files are required by autotools/libtool. For example I don't have those on my Debian system for any packaged library (Debian is not shipping .la files for a long time now), and I don't have any problem. Maybe you did configure geany-plugins at a time the .la file existed, and somehow it then expects to find it? You should try and re-generating the build system, ideally from a clean clone, but maybe simply `make distclean` and then `./autogen.sh` again. If that's not it, are you 100% sure *no* files in your pango installation is referring the .la, possibly an outdated one from before their switch that would still lie somewhere?
Regards, Colomban
On 25 November 2017 at 09:44, Colomban Wendling lists.ban@herbesfolles.org wrote:
Hey Tim,
Le 24/11/2017 à 13:46, Tim Tassonis a écrit :
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
/opt/X11 is a strange location, have you built your own GTK stack?
Those files are not installed anymore with latest pango. Is there a fix or is pango with meson/ninja not supported?
I don't think .la files are required by autotools/libtool. For example I don't have those on my Debian system for any packaged library (Debian is not shipping .la files for a long time now), and I don't have any problem. Maybe you did configure geany-plugins at a time the .la file existed, and somehow it then expects to find it? You should try and re-generating the build system, ideally from a clean clone, but maybe simply `make distclean` and then `./autogen.sh` again. If that's not it, are you 100% sure *no* files in your pango installation is referring the .la, possibly an outdated one from before their switch that would still lie somewhere?
Regards, Colomban _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 11/25/2017 01:09 AM, Lex Trotman wrote:
On 25 November 2017 at 09:44, Colomban Wendling lists.ban@herbesfolles.org wrote:
Hey Tim,
Le 24/11/2017 à 13:46, Tim Tassonis a écrit :
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
/opt/X11 is a strange location, have you built your own GTK stack?
Yes, this is a linux from scratch machine. All my X11 stuff is under /opt/X11 and this works fine, after setting up a few symlinks.
Just if that was not clear: I'm not exactly a newbie to compiling stuff myself and I have previously successfully compiled and installed geany-plugins and geany that way before. It's really the pango switch to meson/ninja that might irritate some packages, as previously I never had an issue.
Might well be that calling ./autoconf.sh fixes all that.
Bye Tim
On 25 November 2017 at 10:28, Tim Tassonis stuff@decentral.ch wrote:
On 11/25/2017 01:09 AM, Lex Trotman wrote:
On 25 November 2017 at 09:44, Colomban Wendling lists.ban@herbesfolles.org wrote:
Hey Tim,
Le 24/11/2017 à 13:46, Tim Tassonis a écrit :
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
/opt/X11 is a strange location, have you built your own GTK stack?
Yes, this is a linux from scratch machine. All my X11 stuff is under /opt/X11 and this works fine, after setting up a few symlinks.
Just if that was not clear: I'm not exactly a newbie to compiling stuff myself and I have previously successfully compiled and installed geany-plugins and geany that way before. It's really the pango switch to meson/ninja that might irritate some packages, as previously I never had an issue.
Might well be that calling ./autoconf.sh fixes all that.
Worth a try, maybe something in your unusual setup confuses autofools.
Bye Tim
Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 11/25/2017 01:31 AM, Lex Trotman wrote:
On 25 November 2017 at 10:28, Tim Tassonis stuff@decentral.ch wrote:
On 11/25/2017 01:09 AM, Lex Trotman wrote:
On 25 November 2017 at 09:44, Colomban Wendling lists.ban@herbesfolles.org wrote:
Hey Tim,
Le 24/11/2017 à 13:46, Tim Tassonis a écrit :
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
/opt/X11 is a strange location, have you built your own GTK stack?
Yes, this is a linux from scratch machine. All my X11 stuff is under /opt/X11 and this works fine, after setting up a few symlinks.
Just if that was not clear: I'm not exactly a newbie to compiling stuff myself and I have previously successfully compiled and installed geany-plugins and geany that way before. It's really the pango switch to meson/ninja that might irritate some packages, as previously I never had an issue.
Might well be that calling ./autoconf.sh fixes all that.
Worth a try, maybe something in your unusual setup confuses autofools.
No, it's really the .la files that cause the trouble, I've now found similar reports from other packages that get into trouble when some .la files reference other .la files that now are missing due to the switch away from libtool. I never liked libtool, anyways..
Removing all .la files fixes the problem.
Sorry for the noise, it's really not geany related.
Bye Tim
On 11/25/2017 12:44 AM, Colomban Wendling wrote:
Hey Tim,
Le 24/11/2017 à 13:46, Tim Tassonis a écrit :
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
Those files are not installed anymore with latest pango. Is there a fix or is pango with meson/ninja not supported?
I don't think .la files are required by autotools/libtool. For example I don't have those on my Debian system for any packaged library (Debian is not shipping .la files for a long time now), and I don't have any problem. Maybe you did configure geany-plugins at a time the .la file existed, and somehow it then expects to find it? You should try and re-generating the build system, ideally from a clean clone, but maybe simply `make distclean` and then `./autogen.sh` again. If that's not it, are you 100% sure *no* files in your pango installation is referring the .la, possibly an outdated one from before their switch that would still lie somewhere?
No, I configured it after the pango upgrade and the .la files did not exist at configure time. I did the usual:
./configure make make install
as I did in the previous geany-plugins versions. However, the ./autogen.sh sounds like a good idea. I could try that, if somebody is interested in the result?
Bye Tim
Regards, Colomban _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
On 11/25/2017 12:44 AM, Colomban Wendling wrote:
Hey Tim,
Le 24/11/2017 à 13:46, Tim Tassonis a écrit :
Pango recently switched from autotools/libtool to meson/ninja and it seems that geany-plugins can't handle that. The compile/install fails on:
/bin/sed: can't read /opt/X11/lib/libpangocairo-1.0.la: No such file or directory libtool: error: '/opt/X11/lib/libpangocairo-1.0.la' is not a valid libtool archive
Those files are not installed anymore with latest pango. Is there a fix or is pango with meson/ninja not supported?
I don't think .la files are required by autotools/libtool. For example I don't have those on my Debian system for any packaged library (Debian is not shipping .la files for a long time now), and I don't have any problem. Maybe you did configure geany-plugins at a time the .la file existed, and somehow it then expects to find it? You should try and re-generating the build system, ideally from a clean clone, but maybe simply `make distclean` and then `./autogen.sh` again. If that's not it, are you 100% sure *no* files in your pango installation is referring the .la, possibly an outdated one from before their switch that would still lie somewhere?
Ok, I searched a bit and it seems that the problem lies with other packages that installed .la files that still referred to the pango .la files. As I have always packaged then in my devel packages, this problem might gonna happed with other packages that link against pango and use libtool.
Cheers Tim