public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] clamav 0.99.4: removed gcc patch
Date: Wed, 07 Mar 2018 18:46:32 +0000	[thread overview]
Message-ID: <1520448392.3332.6.camel@ipfire.org> (raw)
In-Reply-To: <20180307182653.1968-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

Thank you for sending in this one. I didn't even notice that the nightly builds
were broken.

I updated clamav as well and removed both patches since it built without.
However, Peter's patch didn't remove any of them and I thought he at least built
the package.

In addition to your patch, I removed the patch file. Please do this in the
future so that we don't have any unused patch files in src/patches.

Good work!

-Michael

On Wed, 2018-03-07 at 19:26 +0100, Matthias Fischer wrote:
> 'clamav-0.99.3-gcc-6.patch' won't apply.
> 
> Best,
> Matthias
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
>  lfs/clamav | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/lfs/clamav b/lfs/clamav
> index 957788aa0..748c2c371 100644
> --- a/lfs/clamav
> +++ b/lfs/clamav
> @@ -82,7 +82,6 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>  	@$(PREBUILD)
>  	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
>  	cd $(DIR_APP) && patch -Np1 -i $(DIR_SRC)/src/patches/clamav/llvm-
> glibc.patch
> -	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/clamav/clamav-
> 0.99.3-gcc-6.patch
>  	cd $(DIR_APP) && ./configure \
>  		--prefix=/usr \
>  		--disable-zlib-vcheck \

  reply	other threads:[~2018-03-07 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 18:26 Matthias Fischer
2018-03-07 18:46 ` Michael Tremer [this message]
2018-03-11 18:19   ` Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1520448392.3332.6.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox