Date: Sun, 27 Jul 2008 13:23:33 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Jens Rehsack" <rehsack@web.de> Cc: FreeBSD GNOME Users <gnome@freebsd.org> Subject: Re: Help required: how to add a patch to gnome-commmander2 port? Message-ID: <op.ueyqpjft9aq2h7@mezz.mezzweb.com> In-Reply-To: <488CBA19.6090809@web.de> References: <488C563D.2000203@web.de> <op.ueyl031p9aq2h7@mezz.mezzweb.com> <488CBA19.6090809@web.de>
index | next in thread | previous in thread | raw e-mail
On Sun, 27 Jul 2008 13:10:33 -0500, Jens Rehsack <rehsack@web.de> wrote:
> Jeremy Messenger wrote:
>> On Sun, 27 Jul 2008 06:04:29 -0500, Jens Rehsack <rehsack@web.de> wrote:
>>
>>> Hi all,
>>>
>>> I tried to update x11-fm/gnome-commander2/ to it's current version,
>>> but there was an error in the ./configure script.
>>> Piotr sent me a patch (modified version attached with applies cleanly
>>> to the port), but it patched the configure.in and the port assumes
>>> autoconf has been already run.
>>>
>>> Is it enough to add autoconf to the USE_AUTOTOOLS line or do I have
>>> check/add sth. else?
>> You can either patch in configure or configure.in with USE_AUTOTOOLS.
>> If you want to keep patch in configure.in. I would do like this:
>> --------------------------------------------------
>> USE_AUTOTOOLS= autoconf:262:env
>> GNU_CONFIGURE= yes
>> [...]
>> pre-configure:
>> @(cd ${WRKSRC} && ${SETENV} ${AUTOTOOLS_ENV} ${AUTORECONF} -W none)
>> --------------------------------------------------
>
> I've added that.
>
>> In your case, I think run autoreconf is good enough.
>
> Because I'm not very familar with the GNU autotools, I follow your hint.
I forgot to remind you about that if you need to patch in Makefile, be
sure to patch in Makefile.am instead of Makefile.in.
> The port build fine but crashed later. I e-mail the gnome-commander
> mailing-list with anything I can find out.
>
> Thank you very much.
> I don't think, the patch to update the port is wanted as long as it
> crashes, isn't it?
It's not worth to update if this update doesn't work. Once it's fixed,
then it's good to go.
Cheers,
Mezz
> /Jens
--
mezz7@cox.net - mezz@FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.ueyqpjft9aq2h7>