bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#26050: 25.2; configure: no libxml2 support with libxml2 installed


From: Eli Zaretskii
Subject: bug#26050: 25.2; configure: no libxml2 support with libxml2 installed
Date: Fri, 10 Mar 2017 20:49:31 +0200

> From: address@hidden (N. Jackson)
> Cc: address@hidden
> Date: Fri, 10 Mar 2017 13:42:17 -0500
> 
> Sorry, this was a user error.

No worries.

>   configure-test:16329: checking for LIBXML2
>   configure-test:16338: $PKG_CONFIG --exists --print-errors "libxml-2.0 > 
> 2.6.17"
>   Package libxml-2.0 was not found in the pkg-config search path.
>   Perhaps you should add the directory containing `libxml-2.0.pc'
>   to the PKG_CONFIG_PATH environment variable
>   No package 'libxml-2.0' found
>   configure-test:16341: $? = 1
>   configure-test:16361: $PKG_CONFIG --exists --print-errors "libxml-2.0 > 
> 2.6.17"
>   Package libxml-2.0 was not found in the pkg-config search path.
>   Perhaps you should add the directory containing `libxml-2.0.pc'
>   to the PKG_CONFIG_PATH environment variable
>   No package 'libxml-2.0' found
>   configure-test:16364: $? = 1
>   configure-test:16381: result: no
>   No package 'libxml-2.0' found
> 
> Now that everything works, it says:
> 
>   configure:16328: checking for LIBXML2
>   configure:16335: $PKG_CONFIG --exists --print-errors "libxml-2.0 > 2.6.17"
>   configure:16338: $? = 0
>   configure:16352: $PKG_CONFIG --exists --print-errors "libxml-2.0 > 2.6.17"
>   configure:16355: $? = 0
>   configure:16393: result: yes
>   configure:16428: checking for htmlReadMemory in -lxml2
>   configure:16453: gcc -o conftest  -g3 -O2       conftest.c -lxml2 -lxml2 
> -lX11   >&5 
>   configure:16453: $? = 0
>   configure:16462: result: yes
> 
> Is it my imagination, or was there a time in the past when
> configure printed a friendly message suggesting the installation
> of the development package for a library when it failed to find
> something like this?

The configure script still does that, but the above message comes from
pkg-config related tests, not from configure.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]