public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pipping at exherbo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug manual/11873] New: Incompatiblity with make 3.82 Date: Tue, 03 Aug 2010 20:02:00 -0000 [thread overview] Message-ID: <20100803200223.11873.pipping@exherbo.org> (raw) GNU make 3.82 has introduced some backward incompatibilities. As a result, glibc cannot be built with make 3.82. Here's what happens: pipping@bogus ~/glibc-2.11.2/manual $ ~/make-3.82/make -n Makefile:235: *** mixed implicit and normal rules. Stop. pipping@bogus ~/glibc-2.11.2/manual $ Here's what's supposed to happen: pipping@bogus ~/glibc-2.11.2/manual $ ~/make-3.81/make -n pwd=`pwd`; \ /usr/bin/perl libm-err-tab.pl $pwd/.. > libm-err-tmp /bin/sh ../scripts/move-if-change libm-err-tmp libm-err.texi touch stamp-libm-err sed -e 's,[{}],@&,g' \ -e 's,/\*\(@.*\)\*/,\1,g' \ -e 's,/\* *,/* @r{,g' -e 's, *\*/,} */,' \ -e 's/\(@[a-z][a-z]*\)@{\([^}]*\)@}/\1{\2}/g'\ examples/stpcpy.c | expand > stpcpy.c.texi.new mv -f stpcpy.c.texi.new stpcpy.c.texi [..] The offending line is $(objpfx)stubs ../po/manual.pot $(objpfx)stamp%: Current git HEAD has it, too. -- Summary: Incompatiblity with make 3.82 Product: glibc Version: 2.11 Status: NEW Severity: normal Priority: P2 Component: manual AssignedTo: roland at gnu dot org ReportedBy: pipping at exherbo dot org CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11873 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-08-03 20:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-03 20:02 pipping at exherbo dot org [this message] 2010-08-10 4:14 ` [Bug manual/11873] " vapier at gentoo dot org 2010-09-29 23:06 ` vapier at gentoo dot org 2010-09-30 8:24 ` pasky at suse dot cz 2010-09-30 15:25 ` vapier at gentoo dot org
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=20100803200223.11873.pipping@exherbo.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).