public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] LTP build issues
Date: Wed, 02 Aug 2017 10:20:50 +0200	[thread overview]
Message-ID: <87bmnygz31.fsf@our.domain.is.not.set> (raw)
In-Reply-To: <120904092.64905035.1501656185854.JavaMail.zimbra@redhat.com>


Hello,

Jan Stancek writes:

> ----- Original Message -----
>> Hi all,
>>
>> I just pulled latest LTP sources and try to build it for the arm64/ilp32 with
>> toolchain provided by Linaro.
>> http://people.linaro.org/~maxim.kuvyrkov/experimental/preview-cross-aarch64-linux-gnu_ilp32.tar.xz
>>
>> And I see that build fails due to multiple reasons. At first I had to revert
>> patches 817d8095f (Rename linux_syscall_numbers.h to lapi/syscalls.h)
>> and 4d0d149c4 (Remove linux_syscall_numbers.h Makefile)
>> because there'ds no lapi/syscalls.h file, and so build becomes broken.
>
> Did you re-run "make autotools" and "./configure"?
> ./include/lapi/syscalls.h should be generated during configure.

Maybe also try 'make distclean' first, then 'make autotools' etc. I
should have put that in the commit message as it is a change to the
build system itself.

>
> If that still doesn't work, you can try it by hand:
> cd ./include/lapi/syscalls
> ./regen.sh
>
>>
>> There are also other reasons for build failures that dirty-fixed in patch
>> below. Could someone comment it and/or share proper fix?
>
> Can you also post build error messages?
>
> Regards,
> Jan

--
Thank you,
Richard.

  reply	other threads:[~2017-08-02  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 21:39 [LTP] LTP build issues Yury Norov
2017-08-02  6:43 ` Jan Stancek
2017-08-02  8:20   ` Richard Palethorpe [this message]
2017-08-02 13:41     ` Yury Norov
2017-08-02  6:50 ` Maxim Kuvyrkov
2017-08-02 13:44   ` Yury Norov

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=87bmnygz31.fsf@our.domain.is.not.set \
    --to=rpalethorpe@suse.de \
    --cc=ltp@lists.linux.it \
    /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