public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Andrew Senkevich <andrew.n.senkevich@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,  libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Install libm.a as linker script [BZ #20539]
Date: Fri, 09 Dec 2016 18:23:00 -0000	[thread overview]
Message-ID: <87d1h1rmfm.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAMXFM3utwitJ-k-=D2N3j5MqZzee8Uy5eBnSGYU1XzMop1NOMw@mail.gmail.com> (Andrew Senkevich's message of "Fri, 9 Dec 2016 20:41:32 +0300")

On Dez 09 2016, Andrew Senkevich <andrew.n.senkevich@gmail.com> wrote:

> 2016-12-09 18:38 GMT+03:00 Andreas Schwab <schwab@suse.de>:
>> On Dez 07 2016, Andrew Senkevich <andrew.n.senkevich@gmail.com> wrote:
>>
>>> +$(inst_libdir)/libm.a: $(common-objpfx)format.lds \
>>> +                    $(libm) \
>>> +                    $(libmvec) \
>>> +                    $(+force)
>>> +     (echo '/* GNU ld script'; echo '*/';\
>>> +      cat $<; \
>>> +      echo 'GROUP ( $(libdir)/libm-$(lib-version).a $(libdir)/libmvec.a )' \
>>> +     ) > $@.new
>>> +     cp $(objpfx)libm.a $(inst_libdir)/libm-$(lib-version).a
>>
>> A rule should only create the target, nothing else.
>
> Is the following update Ok?

There is no neeed to go through a stamp file, just depend on
$(inst_libdir)/libm-$(lib-version).a, and add a rule which copies
$(objpfx)libm.a there.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2016-12-09 18:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 19:21 Andrew Senkevich
2016-10-24 22:02 ` H.J. Lu
2016-11-14 19:16   ` Andrew Senkevich
2016-11-14 19:22     ` H.J. Lu
2016-12-05 19:40   ` Andrew Senkevich
2016-12-05 20:01     ` H.J. Lu
2016-12-06 12:17       ` Andrew Senkevich
2016-12-06 14:17         ` Andreas Schwab
2016-12-06 14:49           ` Andrew Senkevich
2016-12-06 15:21             ` Andreas Schwab
2016-12-06 15:50               ` Andrew Senkevich
2016-12-06 21:49                 ` H.J. Lu
2016-12-07 10:34                   ` Andrew Senkevich
2016-12-07 16:22                     ` H.J. Lu
2016-12-07 20:04                       ` Andrew Senkevich
2016-12-07 21:50                         ` H.J. Lu
2016-12-09 15:39                         ` Andreas Schwab
2016-12-09 17:42                           ` Andrew Senkevich
2016-12-09 18:23                             ` Andreas Schwab [this message]
2016-12-12 15:45                               ` Andrew Senkevich
2016-12-12 16:18                                 ` Andreas Schwab
2016-12-12 16:29                                   ` Andrew Senkevich
2016-12-12 16:42                                     ` Andreas Schwab
2016-12-12 17:58                                       ` Andrew Senkevich
2016-12-13  8:41                                         ` Andreas Schwab
2016-12-13 14:58                                           ` Andrew Senkevich

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=87d1h1rmfm.fsf@linux-m68k.org \
    --to=schwab@suse.de \
    --cc=andrew.n.senkevich@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@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).