From: Andreas Jaeger <aj@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fixes for make clean (take 2)
Date: Sat, 08 Jan 2005 17:13:00 -0000 [thread overview]
Message-ID: <m3fz1bx2ri.fsf@gromit.moeb> (raw)
In-Reply-To: <20050108170445.GE17169@sunsite.mff.cuni.cz> (Jakub Jelinek's message of "Sat, 8 Jan 2005 18:04:45 +0100")
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
Jakub Jelinek <jakub@redhat.com> writes:
> On Sat, Jan 08, 2005 at 05:49:23PM +0100, Andreas Jaeger wrote:
>> > This seems to work for me:
>>
>> But why is it necessary? Why are we using both
>> tests: $(objpfx)some-test.out
>> and
>> tests += other-test
>>
>> Only the later should be needed AFAIK,
>
> tst-pie1 needs a special rule, because the general rule for building
> tests is unsuitable for building PIE binaries.
Yeah - a special rule not only for execution but also for building.
Now I see...
> If you have the special rule and tests += tst-pie1, then you get the
> make warnings about overriding targets.
Thanks,
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2005-01-08 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 11:11 Fixes for make clean Andreas Jaeger
2005-01-03 16:57 ` Ulrich Drepper
2005-01-07 12:44 ` Jakub Jelinek
2005-01-07 13:58 ` Andreas Jaeger
2005-01-08 16:39 ` [PATCH] Fixes for make clean (take 2) Jakub Jelinek
2005-01-08 16:49 ` Andreas Jaeger
2005-01-08 17:04 ` Jakub Jelinek
2005-01-08 17:13 ` Andreas Jaeger [this message]
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=m3fz1bx2ri.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@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: 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).