Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-23 Thread Ben Kamen 
On 02/23/2018 04:47 AM, Alex Naumov wrote:
> Great!
> I'm going to apply these patches to git today.
> Thanks for testing!
>

More than happy to.

Is there anything else I can provide that'd help in any way?

Just let me know,

 -Ben

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-23 Thread Alex Naumov 
Great!
I'm going to apply these patches to git today.
Thanks for testing!

Cheers,
Alex

On Fri, Feb 23, 2018 at 9:33 AM, Ben Kamen  wrote:
> On 02/22/2018 01:35 PM, Ben Kamen wrote:
>> On 02/22/2018 09:27 AM, Alex Naumov wrote:
>>> On Thu, Feb 22, 2018 at 11:00 AM, Ben Kamen  wrote:
  Is there more information I can provide?

>>> Hey Ben,
>>>
>>> did you try patches (from https://savannah.gnu.org/bugs/?43223)?
>>> Take a look at last comment. There are modified patches.
>> I did not see that previous comment with patch info.
>>
>> Will go try and let ya know.
>>
>> stay tuned and thanks,
>
> That worked fabulously.
>
> (two thumbs up)
>
> need more testing, but I think everything is working.
>
> Thanks!
>
>  -Ben
>

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-23 Thread Ben Kamen 
On 02/22/2018 01:35 PM, Ben Kamen wrote:
> On 02/22/2018 09:27 AM, Alex Naumov wrote:
>> On Thu, Feb 22, 2018 at 11:00 AM, Ben Kamen  wrote:
>>>  Is there more information I can provide?
>>>
>> Hey Ben,
>>
>> did you try patches (from https://savannah.gnu.org/bugs/?43223)?
>> Take a look at last comment. There are modified patches.
> I did not see that previous comment with patch info.
>
> Will go try and let ya know.
>
> stay tuned and thanks,

That worked fabulously.

(two thumbs up)

need more testing, but I think everything is working.

Thanks!

 -Ben

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-22 Thread Ben Kamen 
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.
>

I'm back working on this after running off to work on some other priorities on 
the same project that needs screen.

With that, screen is now my current priority -- and from what I'm reading on 
automake, 'configure' issues are recommended to take to package maintainers.

 Is there more information I can provide?

 I can profile a user login on the host I do all this work from to help you out 
if you'd like.

it looks like this configure.ac/automake just need a little tuning to provide a 
good configure script.

Let me know how I can help?

Thanks,

 -Ben

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-08 Thread Amadeusz Sławiński 
On Thu, 8 Feb 2018 02:49:52 -0600
Ben Kamen  wrote:

> On 02/07/2018 03:53 PM, Ben Kamen wrote:
> > Hey Alex (and all),
> >
> > I did find this (https://how-to-build-for-arm.wikispaces.com/screen) and am 
> > currently absorbing it...
> >
> > it references screen 4.0.3 and I'm at 4.6.2 hopefully changes made it 
> > to current versions?
> >
> > I'll write back with what I find as I work on this later tonight...
> >
> >  
> 
> Nope. that didn't help. The page looks to bypass all the cross compile 
> statements.
> 
> 
> So -- is screen not made to cross-compile at all? (I'm guessing "no"?)
> 
> :( (sad face)
> 
>  -Ben
> 
> 

Hey,

take a look at this bug:
https://savannah.gnu.org/bugs/?43223
some of those patches may help.

Amadeusz

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-08 Thread Ben Kamen 
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//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

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-08 Thread Alex Naumov 
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.

Regards,
Alex

On Fri, Feb 2, 2018 at 10:01 AM, Alex Naumov
 wrote:
>
> how exactly do you try to compile it?
>

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-08 Thread Ben Kamen 
On 02/07/2018 03:53 PM, Ben Kamen wrote:
> Hey Alex (and all),
>
> I did find this (https://how-to-build-for-arm.wikispaces.com/screen) and am 
> currently absorbing it...
>
> it references screen 4.0.3 and I'm at 4.6.2 hopefully changes made it to 
> current versions?
>
> I'll write back with what I find as I work on this later tonight...
>
>

Nope. that didn't help. The page looks to bypass all the cross compile 
statements.


So -- is screen not made to cross-compile at all? (I'm guessing "no"?)

:( (sad face)

 -Ben

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-07 Thread Ben Kamen 
On 02/02/2018 11:47 AM, Ben Kamen wrote:
> On 02/02/2018 03:01 AM, Alex Naumov wrote:
>> Hey,
>>
>> how exactly do you try to compile it? Can you show your config.log?
>> On my Pinebook(aarch64) I have no problem with 4.6.2.
>>
>> Cheers,
>> Alex
>>
>> On Fri, Feb 2, 2018 at 2:04 AM, Ben Kamen  wrote:
>>> Hey all, not sure if the users list is very active or appropriate for this 
>>> question (I tried there first, but so far no response).
>>>
>>> So if it's ok to ask here here's my email to the user's list:
>>>
>>>
 Quick question and hopefully I can be on my way my target is a Xilinx 
 Zynq ARM/FPGA and I've been fine cross compiling other things using a 
 script to set up where my libraries/compiler live and then running 
 configure (inside the script).

 It looks like the test for  check is where things fail.
>>> I updated this to include the ./configure output which says:
>>>
 this is screen version 4.6.2
 checking for arm-xilinx-linux-gnueabi-gcc... arm-xilinx-linux-gnueabi-gcc
 checking whether the C compiler works... yes
 checking for C compiler default output file name... a.out
 checking for suffix of executables...
 checking whether we are cross compiling... yes
 checking for suffix of object files... o
 checking whether we are using the GNU C compiler... yes
 checking whether arm-xilinx-linux-gnueabi-gcc accepts -g... yes
 checking for arm-xilinx-linux-gnueabi-gcc option to accept ISO C89... none 
 needed
 checking how to run the C preprocessor... arm-xilinx-linux-gnueabi-gcc -E
 checking for grep that handles long lines and -e... /bin/grep
 checking for egrep... /bin/grep -E
 checking whether arm-xilinx-linux-gnueabi-gcc needs -traditional... no
 checking for library containing strerror... none required
 checking for ANSI C header files... yes
 checking for sys/types.h... yes
 checking for sys/stat.h... yes
 checking for stdlib.h... yes
 checking for string.h... yes
 checking for memory.h... yes
 checking for strings.h... yes
 checking for inttypes.h... yes
 checking for stdint.h... yes
 checking for unistd.h... yes
 checking minix/config.h usability... no
 checking minix/config.h presence... no
 checking for minix/config.h... no
 checking whether it is safe to define __EXTENSIONS__... yes
 configure: error: in 
 `/d1/home/bkamen/workspace-xilinx/uZed-BSP/components/apps/screen/screen-4.6.2':
 configure: error: cannot run test program while cross compiling
 See `config.log' for more details
>>>
>>> I should add, my Xilinx dev environment is CentOS 6.9 -- although the tools 
>>> being used (the entire cross-compile environment) is PetaLinux 2015.4 (I 
>>> know, old. But once something works in Xilinx, you don't usually want to 
>>> change tools unless REALLY necessary or you have lots of time to work out 
>>> the stuff that breaks.)
>>>
>>> Anyway -- let me know what else I can provide.
>>>
> Here's the config.log (attached)
>
> Thanks for taking a look,
>
>  -Ben
>
Hey Alex (and all),

I did find this (https://how-to-build-for-arm.wikispaces.com/screen) and am 
currently absorbing it...

it references screen 4.0.3 and I'm at 4.6.2 hopefully changes made it to 
current versions?

I'll write back with what I find as I work on this later tonight...


 -Ben

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-02 Thread Ben Kamen 
On 02/02/2018 03:01 AM, Alex Naumov wrote:
> Hey,
>
> how exactly do you try to compile it? Can you show your config.log?
> On my Pinebook(aarch64) I have no problem with 4.6.2.
>
> Cheers,
> Alex
>
> On Fri, Feb 2, 2018 at 2:04 AM, Ben Kamen  wrote:
>> Hey all, not sure if the users list is very active or appropriate for this 
>> question (I tried there first, but so far no response).
>>
>> So if it's ok to ask here here's my email to the user's list:
>>
>>
>>> Quick question and hopefully I can be on my way my target is a Xilinx 
>>> Zynq ARM/FPGA and I've been fine cross compiling other things using a 
>>> script to set up where my libraries/compiler live and then running 
>>> configure (inside the script).
>>>
>>> It looks like the test for  check is where things fail.
>> I updated this to include the ./configure output which says:
>>
>>> this is screen version 4.6.2
>>> checking for arm-xilinx-linux-gnueabi-gcc... arm-xilinx-linux-gnueabi-gcc
>>> checking whether the C compiler works... yes
>>> checking for C compiler default output file name... a.out
>>> checking for suffix of executables...
>>> checking whether we are cross compiling... yes
>>> checking for suffix of object files... o
>>> checking whether we are using the GNU C compiler... yes
>>> checking whether arm-xilinx-linux-gnueabi-gcc accepts -g... yes
>>> checking for arm-xilinx-linux-gnueabi-gcc option to accept ISO C89... none 
>>> needed
>>> checking how to run the C preprocessor... arm-xilinx-linux-gnueabi-gcc -E
>>> checking for grep that handles long lines and -e... /bin/grep
>>> checking for egrep... /bin/grep -E
>>> checking whether arm-xilinx-linux-gnueabi-gcc needs -traditional... no
>>> checking for library containing strerror... none required
>>> checking for ANSI C header files... yes
>>> checking for sys/types.h... yes
>>> checking for sys/stat.h... yes
>>> checking for stdlib.h... yes
>>> checking for string.h... yes
>>> checking for memory.h... yes
>>> checking for strings.h... yes
>>> checking for inttypes.h... yes
>>> checking for stdint.h... yes
>>> checking for unistd.h... yes
>>> checking minix/config.h usability... no
>>> checking minix/config.h presence... no
>>> checking for minix/config.h... no
>>> checking whether it is safe to define __EXTENSIONS__... yes
>>> configure: error: in 
>>> `/d1/home/bkamen/workspace-xilinx/uZed-BSP/components/apps/screen/screen-4.6.2':
>>> configure: error: cannot run test program while cross compiling
>>> See `config.log' for more details
>>
>>
>> I should add, my Xilinx dev environment is CentOS 6.9 -- although the tools 
>> being used (the entire cross-compile environment) is PetaLinux 2015.4 (I 
>> know, old. But once something works in Xilinx, you don't usually want to 
>> change tools unless REALLY necessary or you have lots of time to work out 
>> the stuff that breaks.)
>>
>> Anyway -- let me know what else I can provide.
>>

Here's the config.log (attached)

Thanks for taking a look,

 -Ben

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure --prefix=/home/bkamen/workspace-xilinx/SPEC-uZed-uCPI_FCDP/uZed-BSP/components/apps/screen/build/ --target=arm-xilinx-linux-gnueabi --host=arm-xilinx-linux-gnueabi --program-prefix= CFLAGS=-I/home/bkamen/workspace-xilinx/SPEC-uZed-uCPI_FCDP/uZed-BSP/build/linux/rootfs/stage/usr/include LDFLAGS=-L/home/bkamen/workspace-xilinx/SPEC-uZed-uCPI_FCDP/uZed-BSP/build/linux/rootfs/stage/usr/lib -L/home/bkamen/workspace-xilinx/SPEC-uZed-uCPI_FCDP/uZed-BSP/build/linux/rootfs/stage/lib CPPFLAGS=-I/home/bkamen/workspace-xilinx/SPEC-uZed-uCPI_FCDP/uZed-BSP/build/linux/rootfs/stage/usr/include

## - ##
## Platform. ##
## - ##

hostname = quantum
uname -m = x86_64
uname -r = 2.6.32-696.16.1.el6.centos.plus.x86_64
uname -s = Linux
uname -v = #1 SMP Wed Nov 15 18:52:54 UTC 2017

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch  = x86_64
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /opt/Xilinx/PetaLinux/petalinux-v2015.4-final/tools/linux-i386/petalinux/bin
PATH: /opt/Xilinx/PetaLinux/petalinux-v2015.4-final/tools/common/petalinux/bin
PATH: /opt/Xilinx/PetaLinux/petalinux-v2015.4-final/tools/linux-i386/microblaze-xilinx-elf/bin
PATH: /opt/Xilinx/PetaLinux/petalinux-v2015.4-final/tools/linux-i386/microblazeel-xilinx-linux-gnu/bin
PATH: /opt/Xilinx/PetaLinux/petalinux-v2015.4-final/tools/linux-i386/arm-xilinx-gnueabi/bin
PATH: /opt/Xilinx/PetaLinux/petalinux-v2015.4-final/tools/linux-i386/arm-xilinx-linux-gnueabi/bin
PATH: /opt/Xilinx/PetaLinux/petalinux-v2015.4-final/tools/linux-i386/aarch64-none-elf/bin
PATH:

Re: [screen-devel] Screen 4.6.2: ./configure fails Cross-Compiling to ARM (Xilinx Zynq)

2018-02-02 Thread Alex Naumov 
Hey,

how exactly do you try to compile it? Can you show your config.log?
On my Pinebook(aarch64) I have no problem with 4.6.2.

Cheers,
Alex

On Fri, Feb 2, 2018 at 2:04 AM, Ben Kamen  wrote:
> Hey all, not sure if the users list is very active or appropriate for this 
> question (I tried there first, but so far no response).
>
> So if it's ok to ask here here's my email to the user's list:
>
>
>> Quick question and hopefully I can be on my way my target is a Xilinx 
>> Zynq ARM/FPGA and I've been fine cross compiling other things using a script 
>> to set up where my libraries/compiler live and then running configure 
>> (inside the script).
>>
>> It looks like the test for  check is where things fail.
>
> I updated this to include the ./configure output which says:
>
>> this is screen version 4.6.2
>> checking for arm-xilinx-linux-gnueabi-gcc... arm-xilinx-linux-gnueabi-gcc
>> checking whether the C compiler works... yes
>> checking for C compiler default output file name... a.out
>> checking for suffix of executables...
>> checking whether we are cross compiling... yes
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
>> checking whether arm-xilinx-linux-gnueabi-gcc accepts -g... yes
>> checking for arm-xilinx-linux-gnueabi-gcc option to accept ISO C89... none 
>> needed
>> checking how to run the C preprocessor... arm-xilinx-linux-gnueabi-gcc -E
>> checking for grep that handles long lines and -e... /bin/grep
>> checking for egrep... /bin/grep -E
>> checking whether arm-xilinx-linux-gnueabi-gcc needs -traditional... no
>> checking for library containing strerror... none required
>> checking for ANSI C header files... yes
>> checking for sys/types.h... yes
>> checking for sys/stat.h... yes
>> checking for stdlib.h... yes
>> checking for string.h... yes
>> checking for memory.h... yes
>> checking for strings.h... yes
>> checking for inttypes.h... yes
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking minix/config.h usability... no
>> checking minix/config.h presence... no
>> checking for minix/config.h... no
>> checking whether it is safe to define __EXTENSIONS__... yes
>> configure: error: in 
>> `/d1/home/bkamen/workspace-xilinx/uZed-BSP/components/apps/screen/screen-4.6.2':
>> configure: error: cannot run test program while cross compiling
>> See `config.log' for more details
>
>
>
> I should add, my Xilinx dev environment is CentOS 6.9 -- although the tools 
> being used (the entire cross-compile environment) is PetaLinux 2015.4 (I 
> know, old. But once something works in Xilinx, you don't usually want to 
> change tools unless REALLY necessary or you have lots of time to work out the 
> stuff that breaks.)
>
> Anyway -- let me know what else I can provide.
>
> Thanks!
>
>  -Ben
>
>