This is the mail archive of the elfutils-devel@sourceware.org mailing list for the elfutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] elfclassify tool

From: Florian Weimer <fweimer at redhat dot com>
To: Mark Wielaard <mark at klomp dot org>
Cc: elfutils-devel at sourceware dot org, Panu Matilainen <pmatilai at laiskiainen dot org>
Date: Mon, 29 Jul 2019 16:42:14 +0200
Subject: Re: [PATCH] elfclassify tool
References: <87k1fz8c9q.fsf@oldenburg2.str.redhat.com> <2e6a27c552ae5e365db54ca6b432c77c9ad5b041.camel@klomp.org> <871s22yybt.fsf@oldenburg2.str.redhat.com> <8736mfzhob.fsf@oldenburg2.str.redhat.com> <ce73f5ebf076570ddc0c1dcd57a07ec39b7555b0.camel@klomp.org> <87k1cadpym.fsf@oldenburg2.str.redhat.com> <20190726221124.GA39429@wildebeest.org> <875znl6vqy.fsf@oldenburg2.str.redhat.com> <20190729144021.GD2881@wildebeest.org>

* Mark Wielaard:

>> Regarding the test case, I think if the build target is ELF, it makes
>> sense to check that the elfutils binaries themselves are classified as
>> expected, with the current build flags.  This will detect changes
>> required due to the evolution of the toolchain.
>
> That is what the run-elfclassify-self.sh testcase does I believe.

Ah, I had missed it.  Great, I think this one is covered.

Thanks,
Florian

References:
- Re: [PATCH] elfclassify tool
  - From: Mark Wielaard
- Re: [PATCH] elfclassify tool
  - From: Florian Weimer
- Re: [PATCH] elfclassify tool
  - From: Mark Wielaard
- Re: [PATCH] elfclassify tool
  - From: Florian Weimer
- Re: [PATCH] elfclassify tool
  - From: Mark Wielaard

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]