Bug#36574: marked as done (glibc_2.1.1-0.2(unstable): Little error in debian/rules)
Your message dated 2 May 1999 18:52:59 -0000
with message-id <[🔎] 19990502185259.25215.qmail@master.debian.org>
and subject line Bug#36574: fixed in glibc 2.1.1-2
has caused the attached bug report 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 I'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Ian Jackson
(administrator, Debian bugs database)
Received: (at submit) by bugs.debian.org; 23 Apr 1999 09:39:59 +0000
Received: (qmail 13961 invoked from network); 23 Apr 1999 09:39:58 -0000
Received: from faui20.informatik.uni-erlangen.de (131.188.32.20)
by master.debian.org with SMTP; 23 Apr 1999 09:39:58 -0000
Received: from faui22c.informatik.uni-erlangen.de (faui22c.informatik.uni-erlangen.de [131.188.32.72])
by faui20.informatik.uni-erlangen.de (8.9.1a/8.1.7-FAU) with ESMTP id LAA08217; Fri, 23 Apr 1999 11:39:48 +0200 (MET DST)
Received: (from rnhodek@localhost)
by faui22c.informatik.uni-erlangen.de (8.8.8/8.1.6-FAU) id LAA08725; Fri, 23 Apr 1999 11:39:48 +0200 (MET DST)
Date: Fri, 23 Apr 1999 11:39:48 +0200 (MET DST)
Message-Id: <199904230939.LAA08725@faui22c.informatik.uni-erlangen.de>
From: Roman Hodek <Roman.Hodek@informatik.uni-erlangen.de>
To: submit@bugs.debian.org
Subject: glibc_2.1.1-0.2(unstable): Little error in debian/rules
Reply-to: Roman.Hodek@informatik.uni-erlangen.de
Package: glibc
Version: 2.1.1-0.2
While trying to compile this glibc version for m68k, I stubled over
the following (a retried build after the first one failed):
> make[1]: Entering directory `/usr/local/build/buildd/glibc-2.1.1'
> for stamp in none `ls -1t /usr/local/build/buildd/glibc-2.1.1/build/stamps-m68k/patched-*`; do \
> case "$stamp" in none|/usr/local/build/buildd/glibc-2.1.1/build/stamps-m68k/patched-\*) continue; esac; \
> patch=`echo $stamp | sed -e 's//usr/local/build/buildd/glibc-2.1.1/build/stamps-m68k\/patched-//'`; \
> echo "trying to revert patch $patch ..."; \
> if [ -x /usr/local/build/buildd/glibc-2.1.1/debian/patches/$patch.dpatch ]; then true; else \
> chmod +x /usr/local/build/buildd/glibc-2.1.1/debian/patches/$patch.dpatch; fi; \
> if /usr/local/build/buildd/glibc-2.1.1/debian/patches/$patch.dpatch -unpatch /usr/local/build/buildd/glibc-2.1.1/build/glibc-2.1.1; then \
> echo "reverted $patch patch."; \
> rm -f $stamp; \
> else \
> echo "error in reverting $patch patch."; \
> exit 1; \
> fi; \
> done
> sed: -e expression #1, char 8: Unknown option to 's'
> make[1]: *** [reverse-patches] Error 1
> make[1]: Leaving directory `/usr/local/build/buildd/glibc-2.1.1'
> make: *** [clean] Error 2
The errorneous line here is
patch=`echo $$stamp | sed -e 's/$(stampdir)\/patched-//'`; \
$(stampdir) can (and does) contain slashes, and therefore greatly
confuses sed, because a slash is also the termination char for the
patterns. I'd suggest using something like
patch=`echo $$stamp | sed -e 's;$(stampdir)/patched-;;'`; \
(ok, now assuimg that $(stampdir) won't contain a semicolon...)
Roman
Reply to: