From: Daniel Schultze <kinglag@gmail.com>
To: crossgcc@sourceware.org
Subject: Re: GNU Make
Date: Wed, 15 Jan 2014 22:15:00 -0000 [thread overview]
Message-ID: <CAEsx0Y8rqZ-8Lm-mFnxMT29bmQGpymV1+ZT3yHrF+UTLzhFiUg@mail.gmail.com> (raw)
In-Reply-To: <CAEsx0Y-ZEFVGioKMn+6WbkUjRe9Rd9hOh0kBHds_XG5yV8oPbg@mail.gmail.com>
Guys after working with CT-NG for a bit I found the patch directory
and recreated my patch to work with the existing system:
in $CT_NG/patches/glibc/2.10.1/920-glibc-2.10.1-manual-make.patch
diff -urN glibc-2.10.1-orig/manual/Makefile glibc-2.10.1/manual/Makefile
--- glibc-2.10.1-orig/manual/Makefile 2006-01-07 22:43:47.000000000 -0800
+++ glibc-2.10.1/manual/Makefile 2014-01-15 11:49:08.256982014 -0800
@@ -232,7 +232,11 @@
.PHONY: stubs
stubs: $(objpfx)stubs
endif
-$(objpfx)stubs ../po/manual.pot $(objpfx)stamp%:
+$(objpfx)stamp%:
+ $(make-target-directory)
+ touch $@
+
+$(objpfx)stubs ../po/manual.pot:
$(make-target-directory)
touch $@
On Wed, Jan 15, 2014 at 10:21 AM, Daniel Schultze <kinglag@gmail.com> wrote:
> Hey guys,
>
> I'm new to crosstool-ng, so far it looks like a good utility. I want
> to contribute a patch for glibc 2.10.1 as it will correct its known
> issue with implicit and explicit rules on the same line. Other patches
> can follow the same pattern of moving the rules to separate lines.
>
>
>
> --- glibc-2.10.1/glibc-2.10.1/manual/Makefile-orig 2013-12-06
> 11:03:33.170318872 -0800
> +++ glibc-2.10.1/glibc-2.10.1/manual/Makefile 2013-12-06
> 11:02:35.555022786 -0800
> @@ -232,7 +232,11 @@
> .PHONY: stubs
> stubs: $(objpfx)stubs
> endif
> -$(objpfx)stubs ../po/manual.pot $(objpfx)stamp%:
> +$(objpfx)stamp%:
> + $(make-target-directory)
> + touch $@
> +
> +$(objpfx)stubs ../po/manual.pot:
> $(make-target-directory)
> touch $@
>
> -Dan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-01-15 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 18:21 Daniel Schultze
2014-01-15 22:15 ` Daniel Schultze [this message]
2014-01-15 23:17 ` Yann E. MORIN
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=CAEsx0Y8rqZ-8Lm-mFnxMT29bmQGpymV1+ZT3yHrF+UTLzhFiUg@mail.gmail.com \
--to=kinglag@gmail.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).