Date: Thu, 20 Feb 2003 21:17:43 -0000 (WET) From: "Rui Lopes" <rui@ruilopes.com> To: <corecode@corecode.ath.cx> Cc: <freebsd-ports@freebsd.org> Subject: Re: need help making regexxer port Message-ID: <49669.217.129.151.119.1045775863.squirrel@webmail> In-Reply-To: <20030220190707.4f9c40af.corecode@corecode.ath.cx> References: <52437.217.129.149.44.1045367887.squirrel@webmail> <20030216133644.653fbfce.corecode@corecode.ath.cx> <1131.217.129.151.9.1045407099.squirrel@webmail> <20030220190707.4f9c40af.corecode@corecode.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
Simon 'corecode' Schubert wrote:
>On Sun, 16 Feb 2003 14:51:39 -0000 (WET)
>"Rui Lopes" <rui@ruilopes.com> wrote:
>
>
>>>>When installing my port the binary file gets the name
>>>>"i386-portbld-freebsd5.0-regexxer" and not "regexxer"; this is the
>>>>output from make install,
>>>>
>>>>
>>>you want to:
>>>CONFIGURE_TARGET= --target=${MACHINE_ARCH}-portbld-freebsd${OSREL}
>>>
>>>
>>that is the default "CONFIGURE_TARGET" value, but with that I end up
>>with a binary file named "i386-portbld-freebsd5.0-regexxer" and not
>>"regexxer", so I had to "manually" set "CONFIGURE_TARGET" to a empty
>>value. My question still remains, what is the right thing to do?
>>
>>
>
>no. this is not the default value. look close. once again.
>this is (at the moment) the right thing to do.
>
>
ops, i've failed to see the "--target=" in there.. but, that gives the
same result, a file named "i386-portbld-freebsd5.0-regexxer" and not
"regexxer".
I found the reason for this not working, from gnu configure --help,
System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
--target=TARGET configure for building compilers for TARGET [HOST]
so i've used,
CONFIGURE_TARGET= --build=${MACHINE_ARCH}-portbld-freebsd${OSREL}
and it now install's fine.
I think bsd.port.mk is making something wrong when we have
GNU_CONFIGURE=yes in our port Makefile.
In bsd.port.mk "we" have,
CONFIGURE_SCRIPT?= configure
CONFIGURE_TARGET?= ${MACHINE_ARCH}-portbld-freebsd${OSREL}
CONFIGURE_LOG?= config.log
..if defined(GNU_CONFIGURE)
CONFIGURE_ARGS+= --prefix=${PREFIX} ${CONFIGURE_TARGET}
HAS_CONFIGURE= yes
..endif
I think this should read,
CONFIGURE_SCRIPT?= configure
CONFIGURE_LOG?= config.log
..if defined(GNU_CONFIGURE)
CONFIGURE_TARGET?= --build ${MACHINE_ARCH}-portbld-freebsd${OSREL}
CONFIGURE_ARGS+= --prefix=${PREFIX} ${CONFIGURE_TARGET}
HAS_CONFIGURE= yes
..endif
Makes sense?
I dunno why CONFIGURE_TARGET was outsite the ".if defined(GNU_CONFIGURE)"
block, from the documentation it is only used when GNU_CONFIGURE is
defined; I also searched for usages of CONFIGURE_TARGET (in .mk files) and
didn't find anything, so this might be a safe change, what do you think?
>>about pcre, fbsd port of pcre does not have that option, I need to
>>build pcre from ports using, make install CONFIGURE_ARGS=--enable-utf8
>>
>>
>
>how about submitting a PR that enables building pcre with utf8?
I will do that, I will submit a pcre-utf8 sub-port, i'm just waiting for a
reply of pcre port maintainer.
Thanks,
-- Rui Lopes
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49669.217.129.151.119.1045775863.squirrel>