Re: Problem building/compiling

[Thomas Dickey]

On Wed, Jul 01, 2020 at 09:19:03PM +0100, Chris Green wrote:
> I am trying to compile vile on a web hosting system where I have a
> Linux ssh login account.  The C preprocessor is problematic:-
> 
>     bash-3.2$ pwd
>     /var/sites/o/oasis41.co.uk/tmp/vile-9.8
>     bash-3.2$ ./configure
>     checking build system type... x86_64-unknown-linux-gnu
>     checking host system type... x86_64-unknown-linux-gnu
>     Configuring for linux-gnu
>     checking for gcc... gcc
>     checking for C compiler default output... a.out
>     checking whether the C compiler works... yes
>     checking whether we are cross compiling... no
>     checking for executable suffix... 
>     checking for object suffix... o
>     checking whether we are using the GNU C compiler... yes
>     checking whether gcc accepts -g... yes
>     checking how to run the C preprocessor... /lib/cpp
>     configure: error: C preprocessor "/lib/cpp" fails sanity check
>     bash-3.2$ 

I'd be inclined to see why the test failed.  config.log shows some
information, but getting details requires editing the configure script
(since it doesn't show a diff between actual and expected).  But seeing
config.log would be useful.
 
> Are there any obvious things to try in order to get round this problem?

I'd look to see what version of ncurses is used.
Of course, if it's busybox, there's not much to be done.

If you've got gcc (and ld), you probably have ldd.
ldd run on bash is a quick way to see (I'm using Debian at the moment):

        linux-vdso.so.1 (0x00007ffdf8bc8000)
        libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x00007f0eb364f000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0eb344b000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0eb30ac000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0eb3879000)

"tinfo" is the low-level half of ncurses.  I'd compile vile with another
machine with the right architecture and version of ncurses (generally
ABI 5's are compatible across releases, ABI 6's probably the same but
less often encountered on limited accounts).

Also - you'll need terminal descriptions.  If your remote ssh account
has "infocmp", it's probably workable.

If you don't have ldd and infocmp, it's more work :-)
 
> Alternatively is there a way to create an executable image which
> includes all libraries etc., like appimage format?  The system reports
> its architecture etc. as:-

not easily - there's a lot of platforms, and only half of the ones I use
are Linux-based...

>     bash-3.2$ uname -a
>     Linux shell3.gridhost.co.uk 2.6.32-754.27.1.el6.x86_64 #1 SMP Tue Jan 28 
> 14:11:45 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net

signature.asc
Description: PGP signature