[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#720002: marked as done (busybox: FTBFS with make 3.82)



Your message dated Mon, 9 May 2022 00:24:13 +0300
with message-id <6a37c608-7f1e-5f29-f767-d4c725c15ef1@msgid.tls.msk.ru>
and subject line Re: Bug#720002: busybox: FTBFS with make 3.82
has caused the Debian Bug report #720002,
regarding busybox: FTBFS with make 3.82
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
720002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720002
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: busybox
Version: 1:1.20.0-8.1
Severity: important

>From my pbuilder build log, using a chroot with make 3.82-1 from experimental 
installed:

...
  GEN     libbb/Kbuild
  GEN     libbb/Config.in
make[1]: Leaving directory `/tmp/buildd/busybox-1.20.0/debian/build/udeb'
cat debian/config/pkg/udeb >> debian/build/udeb/.config
/usr/bin/make -C debian/build/udeb oldconfig
make[1]: Entering directory `/tmp/buildd/busybox-1.20.0/debian/build/udeb'
.config:417: *** missing separator.  Stop.
make[1]: *** [scripts_basic] Error 2
make[1]: Leaving directory `/tmp/buildd/busybox-1.20.0/debian/build/udeb'
make: *** [debian/build/udeb/.setup] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler

--- End Message ---
--- Begin Message ---
On Tue, 10 Dec 2013 02:29:49 +0400 Michael Tokarev <mjt@tls.msk.ru> wrote:
Control: tag -1 + moreinfo unreproducible
...
Hmm.  I tried to reproduce this, but can not, neither with 1.20 version
from wheezy nor with 1.21 version from sid, with parallel make or not.

So, after almost 10 years, with current make at version 4.3, I don't
think this bug is relevant anymore.. Closing this bugreport now.

Thanks,

/mjt

--- End Message ---

Reply to: