[schilytools] [RELEASE] 2023-01-12

[Nico Sonack]

On Mon, Jan 16, 2023 at 09:45:53AM -0500, Dennis Clarke via schilytools wrote:
> On 1/16/23 08:56, Nico Sonack wrote:
> > On Mon, Jan 16, 2023 at 08:47:30AM -0500, Dennis Clarke via schilytools wrote:
> >> On 1/16/23 08:44, Nico Sonack wrote:
> >>> On Mon, Jan 16, 2023 at 08:36:31AM -0500, Dennis Clarke via schilytools wrote:
> >>>> 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,
> >>>>>>>
> >>>>>> 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
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> pollux # cat  config.log
> >>>> This file contains any messages produced by compilers while
> >>>> running configure, to aid debugging if configure makes a mistake.
> >>>>
> >>>> 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 #
> >>>>
> >>>
> >>> Unset LIBS in your environment. It's used internally by autoconf
> >>> to keep track of libraries. By setting it you're messing it up
> >>> because it doesn't know where to search for the libraries. Also, I
> >>> believe during the bootstrap of smake you don't need libiconv.
> >>>
> >>> Hope that solves the problem.
> >>>
> >>
> >> This is baffling ... because I was following your notes from a build
> >> last week. Where we did use the LIBS and the new fangled LDOPTX thing.
> > 
> > This is not really surprising. I never set LIBS anywhere when I
> > built on the Solaris machines. LDOPTX I only ever provided directly
> > to the make command.
> > 
> > e.g.:
> > 
> > $ psmake/smake LDOPTX=-L/usr/local/lib\ -Wl,-R/usr/local/lib\ -liconv
> > 
> > For more details about options you can give make see the README.compile.
> 
> Sure enough the compile fails :
> 
> .
> .
> .
>          ==> LINKING "OBJ/sparc-sunos5-gcc/mkisofs"
> Undefined                       first referenced
>   symbol                             in file
> libiconv_close 
> ../libs/sparc-sunos5-gcc/libsiconv.a(sic_nls.o)
> libiconv_open 
> ../libs/sparc-sunos5-gcc/libsiconv.a(sic_nls.o)
> libiconv                            OBJ/sparc-sunos5-gcc/joliet.o
> ld: fatal: symbol referencing errors. No output written to 
> OBJ/sparc-sunos5-gcc/mkisofs
> collect2: error: ld returned 1 exit status
> smake: *** Code 1 (Not owner) from command line for target 
> 'OBJ/sparc-sunos5-gcc/mkisofs'.
> smake: The following command caused the error:
> echo "  ==> LINKING \"OBJ/sparc-sunos5-gcc/mkisofs\""; gcc  -o 
> OBJ/sparc-sunos5-gcc/mkisofs -L../libs/sparc-sunos5-gcc 
> -L../libs/sparc-sunos5-gcc  -L/opt/schily/lib -Wl,-R/opt/schily/lib 
> -Wl,-R/opt/schily/lib  OBJ/sparc-sunos5-gcc/mkisofs.o 

You removed the LDOPTX. I suggested to only remove LIBS and not LDOPTX.

> So I wonder what happens if I install the Sun/Oracle Studio tools?

That won't solve the problem either.

Again, see README.compile.

Nico

-- 
Sent from triton / FreeBSD 13.1-RELEASE

Please remember: https://useplaintext.email/#etiquette
HTML-formatted mail will likely end up in the Spam folder.
Do NOT send me Microsoft Office documents. I shall refrain from opening
them.

Nico Sonack <nsonack at herrhotzenplotz.de>