[schilytools] [RELEASE] 2023-01-12

[Dennis Clarke]

On 1/16/23 08:25, Nico Sonack wrote:
> On Mon, Jan 16, 2023 at 08:13:36AM -0500, Dennis Clarke via schilytools wrote:
>> On 1/12/23 09:33, Robert Clausecker wrote:
>>> Dear schilytools users,
>>>
>>> I am proud to present the 2023-01-12 release of schilytools.
>>> We have been very busy preparing this release with many new
>>> features and hope that you find it useful.
>>>
>>> Obtain the release tarball schily-2023-01-12.tar.bz2 from:
>>>
>>
>> Fails to build on a Solaris 10 server with gcc :
>>
>> pollux #
>> pollux # pwd
>> /root/schily-2023-01-12/psmake
>> pollux #
>> pollux # /usr/bin/time -p /usr/xpg4/bin/nice -n +18 ./MAKE-all
>> Checking for working bootstrap make...
>> ./MAKE-all: ./smake: not found
>> Creating bootstrap make...
>> Removing old objects...
>> Removing old config cache files...
>> done.
>> Checking for source files...
>> Source files are not present...
>> Creating links to source files...
>> Checking for rotten symlinks...
>> testing for uname...
>> Trying to find GCC
>> SYSTEM:         SunOS
>> CC:             gcc
>> OPT:            -O
>> CPPFLAGS:
>> CFLAGS:
>> INCLUDE:        -Iinclude -I.
>> CONFIG_SHELL:   sh
>>
>> configure: error: installation or configuration problem: C compiler
>> cannot creat
>> e executables.
> 
> Looks like your compiler options (either in the environment or as given by
> the configure script) are broken. Check psmake/config.log.
> 
> Nico
> 
> 


The config.log was pretty cute :


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

configure:913: checking host system type
configure:935: checking if sh is bash
configure:957: checking if /bin/sh is bash
configure:979: checking whether sh -ce is broken
configure:1001: checking whether /bin/sh -ce is broken
configure:1023: checking whether /bin/bosh is a working shell
configure:1050: checking whether /opt/schily/bin/bosh is a working shell
configure:1079: checking for cc
configure:1108: checking for gcc
configure:1221: checking whether the C compiler (gcc  ) works
configure:1247: gcc -o conftest   conftest.c  -liconv 1>&5
ld: fatal: library -liconv: not found
ld: fatal: file processing errors. No output written to conftest
collect2: error: ld returned 1 exit status
configure: failed program was:

#line 1242 "configure"
#include "confdefs.h"

int main(){return(0);}
pollux #


Of course I have that :

pollux # ls /usr/local/lib/libicon*
/usr/local/lib/libiconv.a         /usr/local/lib/libiconv.so.2
/usr/local/lib/libiconv.la        /usr/local/lib/libiconv.so.2.6.0
/usr/local/lib/libiconv.so
pollux #


In any case I thought the LDOPTX was the deal there.





-- 
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional