From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix checking of ld.so undefined symbols on sparc64
Date: Thu, 16 Aug 2007 21:17:00 -0000 [thread overview]
Message-ID: <20070816211648.8405F4D0461@magilla.localdomain> (raw)
In-Reply-To: Jakub Jelinek's message of Thursday, 16 August 2007 22:33:51 +0200 <20070816203351.GD2279@sunsite.mff.cuni.cz>
> On Thu, Aug 16, 2007 at 01:23:03PM -0700, Roland McGrath wrote:
> > Might as well just use { print; exit 2 } in the awk.
>
> Well, that would print just one line, we want to see all undefined
> symbols, don't we?
> But
> awk '($7 ~ /^UND(|EF)$/ && $1 != "0:" && $4 != "REGISTER") { print; p=1 } END { exit p != 0 }'
> could work...
Sure. I just meant no need for the cmp when using awk.
prev parent reply other threads:[~2007-08-16 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 20:13 Jakub Jelinek
2007-08-16 20:23 ` Roland McGrath
2007-08-16 20:28 ` Jakub Jelinek
2007-08-16 21:17 ` Roland McGrath [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=20070816211648.8405F4D0461@magilla.localdomain \
--to=roland@redhat.com \
--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).