From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] cross compilation failing
Date: Tue, 16 Jan 2018 12:51:20 +0100 [thread overview]
Message-ID: <20180116115120.GC24595@rei> (raw)
In-Reply-To: <CAN9dZwcYaD89iQ8pTRGjB5bG3H4JrkdgD9M22d5fxyQjpSyNEQ@mail.gmail.com>
Hi!
> *For X86_64 :*
> if executing testcases on x86_64 "GLIBC_2.14 not found" giving.
>
> # sh network.sh -6
> tst_net_ip_prefix: /lib64/libc.so.6: version `GLIBC_2.14' not found
> (required by tst_net_ip_prefix)
> tst_net_ip_prefix: /lib64/libc.so.6: version `GLIBC_2.13' not found
> (required by tst_net_ip_prefix)
This looks like you have compiled the binaries on different distribution
(quite likely against different libc) than you attempt to run them on,
which will not work for obvious reasons.
> *For MIPS:*
> following steps performed for cross compilation.
> 1) make autotools
> 2) ./configure --prefix=/var/fpwork/rahul_gupta/ltp_ampp/ltp-master/fpt18
> CXX=${CROSS_COMPILE}g++ CC=${CROSS_COMPILE}gcc AS=${CROSS_COMPILE}as
> AR=${CROSS_COMPILE}ar LD=${CROSS_COMPILE}ld NM=${CROSS_COMPILE}nm
> OBJCOPY=${CROSS_COMPILE}objcopy OBJDUMP=${CROSS_COMPILE}objdump
> RANLIB=${CROSS_COMPILE}ranlib READELF=${CROSS_COMPILE}readelf
> STRIP=${CROSS_COMPILE}strip --host=mips-wrs-linux-gnu
> --build=i586-wrs-linux-gnu
AFAIK ou are supposed only to define the CROSS_COMPILE and --host here,
which may cause the failure.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-01-16 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 10:02 [LTP] cross compilation failing rahul gupta
2018-01-16 10:38 ` Cyril Hrubis
2018-01-16 10:53 ` rahul gupta
2018-01-16 11:51 ` Cyril Hrubis [this message]
2018-01-17 8:14 ` Petr Vorel
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=20180116115120.GC24595@rei \
--to=chrubis@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.