[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to AR
From: |
Ben Kamen |
Subject: |
Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq) |
Date: |
Thu, 8 Feb 2018 04:38:07 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 |
On 02/08/2018 03:48 AM, Alex Naumov wrote:
> Please provide more info how do you trying to compile it.
> Did you try to compile something else in your CC environment?
> Let us know how to reproduce it exactly like you doing it.
>
>
Xilinx has their own rollup of an arm cross compiler they call PetaLinux. (IIRC
it's an older variant of Yocto/OpenEmbedded).
So that whole mess I have installed in
/opt/Xilinx/Petalinux/<someversion>/complete-toolchaindirectory.
Xilinx wants you to set an ENV var to point to that directory above so all it's
canned scripts like "petalinux-build" work.
With other programs like openntp and htop, I've made a semi-custom script that
sets up stuff I need and looks like this:
> #!/bin/sh
> #
> # This file helps set up just about any external project to use the
> Zynq/Petalinux install/build tree.
> # It really needs to be set to a current zynq build directory... (see below)
>
> # Sets the PREFIX for installing stuff into some known place that's NOT your
> computer's System Directories.
> MYDIR=~/workspace-xilinx/SPEC-uZed-uCPI_FCDP/uZed-BSP/components/apps/screen/build/
>
> # This points to a current working Zynq build directory
> ZYNQDIR=~/workspace-xilinx/SPEC-uZed-uCPI_FCDP/uZed-BSP/build/linux/rootfs/stage
>
>
> ./configure \
> --prefix=$MYDIR \
> --host=arm-xilinx-linux-gnueabi \
> --target=arm-xilinx-linux-gnueabi \
> --enable-colors256 \
> CFLAGS="-I$ZYNQDIR/usr/include" \
> LDFLAGS="-L$ZYNQDIR/usr/lib -L$ZYNQDIR/lib" \
> CPPFLAGS="-I$ZYNQDIR/usr/include" \
> $1
>
This particular one is what I'm using for screen --- obviously I have to edit
it for each thing I want to build (htop, openntp, and so on..)
That's how configure for screen gets run.
The logfile I sent you is what I get with the default 'configure' that's
included in screen-4.6.2.tar.gz
It looks like the configure script has been set to bail on cross compiling in
general.
And not being an autoconf person, that's where I'm stuck.
-Ben
p.s. The target is a Xilinx Zynq SoC with a dual-core ARM-A9 CPU running (uname
-a):
Linux uZed 4.0.0-xilinx #8 SMP PREEMPT Wed Feb 7 21:08:10 CST 2018 armv7l
GNU/Linux
- [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Ben Kamen, 2018/02/01
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Alex Naumov, 2018/02/08
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq),
Ben Kamen <=
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Ben Kamen, 2018/02/22
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Alex Naumov, 2018/02/22
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Ben Kamen, 2018/02/22
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Ben Kamen, 2018/02/23
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Alex Naumov, 2018/02/23
- Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq), Ben Kamen, 2018/02/23