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 2/3] dhcp: update lfs file after gzip update to fix build  fail
Date: Tue, 08 Mar 2016 17:06:43 +0000	[thread overview]
Message-ID: <1457456803.6973.136.camel@ipfire.org> (raw)
In-Reply-To: <a1d53b8c882539340a81ef1bdcbdb1b5@mail01.ipfire.org>

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

I think this *should not* break. This might be a regression in gzip
then.

Do you have a snippet of the build log of the error?

-Michael

On Tue, 2016-03-08 at 18:03 +0100, Marcel Lorenz wrote:
> Am 2016-03-08 15:26, schrieb Michael Tremer:
> > Hi,
> > 
> > what is the build issue you are trying to solve here?
> > 
> > Copying in a highly outdated version of the bind libs is from my
> > point
> > of view a big security risk.
> > 
> > -Michael
> > 
> > On Tue, 2016-03-08 at 11:09 +0100, Marcel Lorenz wrote:
> > > Signed-off-by: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
> Hi,
> 
> you have right, the old bind is a security risk!
> 
> This is the current lfs file without patch:
> *****
> 	cd $(DIR_APP) && patch -Np1 < 
> $(DIR_SRC)/src/patches/dhcp/dhcp-stateless-DUID-LLT.patch
> 
> 	# Remove bundled BIND stuff.
> 	# (requires newer autoconf)
> 	#rm -rfv $(DIR_APP)/bind/bind.tar.gz
> 	#cd $(DIR_APP) && autoreconf --verbose --force --install
> 
> 	cd $(DIR_APP) && \
> *****
> 
> The error in log is "use tar axf to extract..."
> 
> The old bind is extracted while make runs. After gzip update this
> not 
> working more automatic.
> They only need some files from bind archive to built the isc-dhcp 
> package. Bind itself is not used.
> (When i understood this correct)
> 
> The: "cd $(DIR_APP)/bind && tar -axf bind.tar.gz" extract this
> before 
> make runs.. That's all..
> 
> Greetings,
> Marcel
> 
> 
> > > 
> > > ---
> > >  lfs/dhcp | 10 ++--------
> > >  1 file changed, 2 insertions(+), 8 deletions(-)
> > > 
> > > diff --git a/lfs/dhcp b/lfs/dhcp
> > > index 9a89d40..cec8628 100644
> > > --- a/lfs/dhcp
> > > +++ b/lfs/dhcp
> > > @@ -99,17 +99,11 @@ $(TARGET) : $(patsubst
> > > %,$(DIR_DL)/%,$(objects))
> > >  	cd $(DIR_APP) && patch -Np1 <
> > > $(DIR_SRC)/src/patches/dhcp/dhcp-gpxe-cid.patch
> > >  	cd $(DIR_APP) && patch -Np1 <
> > > $(DIR_SRC)/src/patches/dhcp/dhcp-stateless-DUID-LLT.patch
> > >  
> > > -	# Remove bundled BIND stuff.
> > > -	# (requires newer autoconf)
> > > -	#rm -rfv $(DIR_APP)/bind/bind.tar.gz
> > > -	#cd $(DIR_APP) && autoreconf --verbose --force --install
> > > -
> > > -	cd $(DIR_APP) && \
> > > -		./configure \
> > > +	cd $(DIR_APP)/bind && tar -axf bind.tar.gz
> > > +	cd $(DIR_APP) && ./configure \
> > >  			--prefix=/usr \
> > >  			--sysconfdir=/etc/dhcp \
> > >  			--with-srv-lease-
> > > file=/var/state/dhcp/dhcpd.leases \
> > > -			--disable-static \
> > >  			--enable-paranoia \
> > >  			--enable-early-chroot \
> > >  			--disable-dhcpv6
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-03-08 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 10:09 [PATCH 1/3] gzip: update to 1.6 Marcel Lorenz
2016-03-08 10:09 ` [PATCH 2/3] dhcp: update lfs file after gzip update to fix build fail Marcel Lorenz
2016-03-08 14:26   ` Michael Tremer
2016-03-08 17:03     ` Marcel Lorenz
2016-03-08 17:06       ` Michael Tremer [this message]
2016-03-08 17:18         ` Marcel Lorenz
2016-03-08 22:39           ` Michael Tremer
2016-03-09 13:34             ` Michael Tremer
2016-03-08 10:09 ` [PATCH 3/3] binutils: fix rootfiles after gzip update (check rootfile msg) Marcel Lorenz

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=1457456803.6973.136.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