On Tue, 2022-12-20 at 14:59 +0100, Mark Wielaard wrote:
> The attached patch does that so no relative paths are needed in
> #include statements.
The try-bot looked good:
https://builder.sourceware.org/buildbot/#/changes/16025
So I pushed this:
commit 6ecd16410ce1fe5cb0ac5b7c3342c5cc330e3a04
Au
Hi,
On Sat, 2022-12-17 at 05:19 +0800, 罗勇刚(Yonggang Luo) wrote:
> On Fri, Oct 28, 2022 at 7:35 PM Mark Wielaard wrote:
> >
> > On Fri, 2022-10-21 at 02:25 +0800, Yonggang Luo via Elfutils-devel
> > wrote:
> > > Because all source in libebl #include , so #include
> > > in
> > > libeblP.h is enou
On Fri, Oct 28, 2022 at 7:35 PM Mark Wielaard wrote:
>
> On Fri, 2022-10-21 at 02:25 +0800, Yonggang Luo via Elfutils-devel
> wrote:
> > Because all source in libebl #include , so #include
> > in
> > libeblP.h is enough, there is multiple memory-access.h file, so use
> > relative path to
> > incl
On Fri, 2022-10-21 at 02:25 +0800, Yonggang Luo via Elfutils-devel
wrote:
> Because all source in libebl #include , so #include
> in
> libeblP.h is enough, there is multiple memory-access.h file, so use
> relative path to
> include it properly,
I am not a fan of the relative path trick, especiall
Because all source in libebl #include , so #include in
libeblP.h is enough, there is multiple memory-access.h file, so use relative
path to
include it properly,
Signed-off-by: Yonggang Luo
-#include
-#include
#include
#include
#include
+
#include
#define AUXV_TYPES
