Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Apr 2002 11:00:58 +0300 (EEST)
From:      Maxim Sobolev <sobomax@FreeBSD.org>
To:        lioux@FreeBSD.ORG (Mario Sergio Fujikawa Ferreira)
Cc:        marcus@FreeBSD.ORG (Joe Marcus Clarke), gnome@FreeBSD.ORG
Subject:   Re: libxml2 issue? (was Re: Ogle patch)
Message-ID:  <200204130800.g3D80wZ25831@vega.vega.com>
In-Reply-To: <no.id> from "Mario Sergio Fujikawa Ferreira" at Apr 12, 2002 11:34:09 PM

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> 
> --ibTvN161/egqYuK8
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> 
> Hi,
> 
> On Fri, Apr 12, 2002 at 09:10:53PM -0300, Joe Marcus Clarke wrote:
> > With the latest libxml2, ogle doesn't want to make configure very well. 
> > This patch seems to fix it.  May I commit it?
> 
> 	Thanks for the heads up. I would prefer, though, a slightly
> different version, a perl regexp.
> 
> 	From my point of view, this is an issue with libxml2 port.
> A closer look at
> 
> libxml.m4 shipped with libxml2-2.4.19
> 
> has the same
> 
> #include <xmlversion.h>
> 
> instead of
> 
> #include <libxml/xmlversion.h>
> 
> 
> 	However, I would advise against "patching" libxml.m4
> because that would cause any configure scripts generated by FreeBSD
> users to be FreeBSD specific which we should strongly discourage.
> 
> 	I am saying this but I do not follow discussions on libxml2
> so it is possible that libxml2 developers will be changing their
> standard in a new future. If they are not, we should "fix" our
> libxml2 to so that we do not need to be patching several configure
> scripts due to libxml2
> 
> 	My suggestion would be to patch xml2-config to include
> the libxml as well. Check the attached patch.

No, www.libxml.org says that `#include <libxml/...>' is The Only True
Way[tm] both for 1.x.x and 2.x.x versions of libxml. We shouldn't
encourage noncompliant behaviour.

> 
> 	Therefore, I would ask Marcus to wait a day or two
> while gnome maintainers discuss what is the best way to handle this.
> If they patch libxml2, nothing needs to be done regarding ogle. By
> the way, I verified that ogle configures/builds just fine by patching
> libxml2
> 
> 	Another portability issue: gtk.m4 installed by gtk12.
> It is FreeBSD specific, configure scripts generated with it
> do not work in other systems. I strongly urge the attached patch
> to be added. It works with autoconf both 2.53 and 2.13. It should
> be send back to gtk12 developers.

I'll look into it. Actually we could just remove that patch completely,
because all FreeBSD ports cope with the problem by setting GTK_CONFIG
environment variable.

Thanks!

-Maxim

> 
> 	Regards,
> 
> -- 
> Mario S F Ferreira - DF - Brazil - "I guess this is a signature."
> Computer Science Undergraduate | FreeBSD Committer | CS Developer
> flames to beloved devnull@someotherworldbeloworabove.org
> feature, n: a documented bug | bug, n: an undocumented feature
> 
> --ibTvN161/egqYuK8
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: attachment; filename=patch-ogle:Makefile
> 
> --- ogle/Makefile.orig	Fri Apr 12 22:52:26 2002
> +++ ogle/Makefile	Fri Apr 12 23:23:15 2002
> @@ -49,6 +49,8 @@
>  		${WRKSRC}/configure.in
>  .endif
>  	@${PERL} -pi -e "s|%%X11BASE%%|${X11BASE}|" ${WRKSRC}/scripts/ogle.in
> +	@${PERL} -pi -e 's|(xmlversion.h>)|libxml/\1|' \
> +		${CONFIGURE_WRKSRC}/${CONFIGURE_SCRIPT}
>  
>  pre-configure:
>  	@${TOUCH} `find -E ${WRKSRC} -regex ".*Makefile\.(am|in)"`
> 
> --ibTvN161/egqYuK8
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: attachment; filename=patch-libxml2:Makefile
> 
> --- libxml2/Makefile.orig	Fri Apr 12 23:22:27 2002
> +++ libxml2/Makefile	Fri Apr 12 23:24:16 2002
> @@ -7,6 +7,7 @@
>  
>  PORTNAME=	libxml2
>  PORTVERSION=	2.4.19
> +PORTREVISION=	1
>  CATEGORIES=	textproc gnome
>  MASTER_SITES=	${MASTER_SITE_GNOME}
>  MASTER_SITE_SUBDIR=	stable/sources/libxml
> @@ -49,5 +50,9 @@
>  pre-patch:
>  	@find ${WRKSRC} -name Makefile.in | xargs ${PERL} -pi -e \
>  		's|\$\(libdir\)/pkgconfig|\$\(prefix\)/libdata/pkgconfig|g'
> +
> +post-patch:
> +	${PERL} -pi.orig -e 's|(\@XML_INCLUDEDIR\@)|\1\
> +		-I\$${includedir}/libxml2/libxml|' ${WRKSRC}/xml2-config.in
>  
>  .include <bsd.port.mk>
> 
> --ibTvN161/egqYuK8
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: attachment; filename="patch-gtk12:files:patch-gtk.m4"
> 
> diff -ruN gtk12.orig/files/patch-gtk.m4 gtk12/files/patch-gtk.m4
> --- gtk12.orig/files/patch-gtk.m4	Fri Feb  9 13:10:45 2001
> +++ gtk12/files/patch-gtk.m4	Fri Apr 12 23:30:05 2002
> @@ -1,11 +1,11 @@
> ---- gtk.m4.orig	Fri Feb  9 22:56:43 2001
> -+++ gtk.m4	Fri Feb  9 22:57:20 2001
> +--- gtk.m4.orig	Thu Feb 18 14:43:13 1999
> ++++ gtk.m4	Fri Apr 12 23:29:51 2002
>  @@ -37,7 +37,7 @@
>        fi
>     fi
>   
>  -  AC_PATH_PROG(GTK_CONFIG, gtk-config, no)
> -+  AC_PATH_PROG(GTK_CONFIG, gtk-config, gtk12-config, no)
> ++  AC_PATH_PROGS(GTK_CONFIG, [gtk-config gtk12-config], no)
>     min_gtk_version=ifelse([$1], ,0.99.7,$1)
>     AC_MSG_CHECKING(for GTK - version >= $min_gtk_version)
>     no_gtk=""
> 
> --ibTvN161/egqYuK8--
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-gnome" in the body of the message
> 
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-gnome" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204130800.g3D80wZ25831>