Date: Thu, 8 Sep 2005 20:21:57 -0500 From: Brian Kee <brianakee@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: Makefile: Trouble with EXTRA_PATCHES Message-ID: <34bd75410509081821d0ba413@mail.gmail.com> In-Reply-To: <34bd754105090816056787df26@mail.gmail.com> References: <34bd7541050908152822793651@mail.gmail.com> <34bd754105090816056787df26@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, a simple segment like the following resolved my problem.
pre-patch:
${SED} -i .orig -e s,file.c,path/to/file.c, ${EXTRA_PATCHES}
I placed this within the .if/.endif block for the specific patch.
I will not say that this is elegant, but it solved the current problem. No=
w=20
on to the next one...
Thank You,=20
Brian A. Kee
On 9/8/05, Brian Kee <brianakee@gmail.com> wrote:=20
>=20
> Well, I found a fairly simple solution the problem. If I manually modify=
=20
> the patch file and add the correct relative path to the file listing in t=
he=20
> top couple of lines within the patch file.=20
> e.g.
> -- filetopatch.c
> changed to
> -- src/filetopatch.c
> the problem corrects itself.=20
> So, I now have two options.=20
> 1. I can contact the maintainer of this patch and have him make these=20
> corrections.
> 2. Somehow figure out how to directly modify this file from within the=20
> Makefile.
> Any suggestions on how this can be accomplished within the Makefile?
> Maybe a post-extract or pre-patch command? I see some referenced command=
=20
> within bsd.port.mk <http://bsd.port.mk/>, but I do not see them defined=
=20
> anywhere.
>=20
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34bd75410509081821d0ba413>