Gentoo Archives: gentoo-dev

From: "vivo75@×××××.com" <vivo75@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: gentoo-x86 commit in dev-perl/XML-Parser: XML-Parser-2.410.0-r1.ebuild ChangeLog
Date: Wed, 08 Aug 2012 21:06:07
Message-Id: 5022D451.9000404@gmail.com
In Reply to: [gentoo-dev] Re: gentoo-x86 commit in dev-perl/XML-Parser: XML-Parser-2.410.0-r1.ebuild ChangeLog by Fabian Groffen
1 Il 07/08/2012 18:26, Fabian Groffen ha scritto:
2 > On 07-08-2012 18:03:14 +0200, Torsten Veller wrote:
3 >> * "Fabian Groffen (grobian)"<grobian@g.o>:
4 >>> grobian 12/08/07 15:21:54
5 >>>
6 >>> Modified: ChangeLog
7 >>> Added: XML-Parser-2.410.0-r1.ebuild
8 >>> Log:
9 >>> Fix expat detection for FreeBSD that silently went unnoticed.
10 >> The following single quotes were dropped:
11 >>
12 >> -myconf="EXPATLIBPATH='${EPREFIX}/usr/$(get_libdir)' EXPATINCPATH='${EPREFIX}/usr/include'"
13 >> +myconf="EXPATLIBPATH=${EPREFIX}/usr/$(get_libdir) EXPATINCPATH=${EPREFIX}/usr/include"
14 >>
15 >> Sorry, I don't understand the problem. Is it a general problem with
16 >> the single quote or a special FreeBSD problem?
17 > I've only observed it happening on FreeBSD indeed.
18 does this work?
19 myconf="\"EXPATLIBPATH=${EPREFIX}/usr/$(get_libdir)\"
20 \"EXPATINCPATH=${EPREFIX}/usr/include\""
21
22 and does thos work with spaces in EPREFIX, are they allowed in there at all?
23 myconf="EXPATLIBPATH=${EPREFIX}/usr/$(get_libdir)
24 EXPATINCPATH=${EPREFIX}/usr/include"
25
26 >
27 >> I think we should convert all myconf strings to arrays:
28 >> myconf=( EXPATLIBPATH="${EPREFIX}"/usr/$(get_libdir) EXPATINCPATH="${EPREFIX}"/usr/include )
29 > I don't understand enough of the Makefile.PL thing to tell why the
30 > quotes work on Darwin, Solaris, but not FreeBSD 9.1-BETA1. I do know
31 > that EPREFIX cannot contain spaces though, hence I applied the fix as
32 > committed. If the array approach works with the eclass, then that'll be
33 > certainly cleaner.
34 yep