POV-Ray : Newsgroups : povray.unix : C compiler cannot create executables Server Time
24 Sep 2021 05:58:50 EDT (-0400)
  C compiler cannot create executables (Message 1 to 5 of 5)  
From: Cousin Ricky
Subject: C compiler cannot create executables
Date: 6 Sep 2021 18:35:00
Message: <web.6136964b11a53c9a60e0cc3d949c357d@news.povray.org>
I just got a new computer, and due to library incompatibilities, I have to
recompile all my POV 3.7 and up executables.  The configure stage halts with
this message:

----------[BEGIN MESSAGE]----------
===============================================================================
Configure POV-Ray version 3.8.0-beta.2
===============================================================================

This is an unofficial version compiled by:
 Richard Callwood III <REDACTED>
The POV-Ray Team(tm) is not responsible for supporting this version.

Environment
-----------
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether $C_INCLUDE_PATH contains the "." path... no
checking whether $CPLUS_INCLUDE_PATH contains the "." path... no
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/ricky/povray/povunix-v3.8.0-beta.2-src':
configure: error: C compiler cannot create executables
See `config.log' for more details
-----------[END MESSAGE]-----------

The relevant parts of config.log appear to be these:

----------[BEGIN LOG EXCERPTS]----------
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by POV-Ray configure 3.8.0-beta.2, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure COMPILED_BY=Richard Callwood III <REDACTED> LIBS=-lboost_system
-lboost_thread

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

hostname = localhost.localdomain
uname -m = x86_64
uname -r = 5.3.18-59.19-default
uname -s = Linux
uname -v = #1 SMP Tue Aug 3 14:11:23 UTC 2021 (055c4fd)

/usr/bin/uname -p = x86_64
/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: /home/ricky/bin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin

....

configure:5179: $? = 1
configure:5199: checking whether the C compiler works
configure:5221: gcc    conftest.c -lboost_system -lboost_thread >&5
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot
find -lboost_system
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot
find -lboost_thread
collect2: error: ld returned 1 exit status
configure:5225: $? = 1
configure:5263: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "POV-Ray"
| #define PACKAGE_TARNAME "povray"
| #define PACKAGE_VERSION "3.8.0-beta.2"
| #define PACKAGE_STRING "POV-Ray 3.8.0-beta.2"
| #define PACKAGE_BUGREPORT "uni### [at] povrayorg"
| #define PACKAGE_URL ""
| #define VERSION_BASE "3.8"
| #define BUILT_BY "Richard Callwood III <REDACTED>"
| #define PACKAGE "povray"
| #define VERSION "3.8.0-beta.2"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:5268: error: in `/home/ricky/povray/povunix-v3.8.0-beta.2-src':
configure:5270: error: C compiler cannot create executables
See `config.log' for more details

....
-----------[END LOG EXCERPTS]-----------

Checks for Boost and the compilers yield:

----------[BEGIN SESSION]----------
ricky@localhost:~/povray/povray-3.7.1-rc.1> type gcc
gcc is /usr/bin/gcc
ricky@localhost:~/povray/povray-3.7.1-rc.1> type g++
g++ is /usr/bin/g++
ricky@localhost:~/povray/povray-3.7.1-rc.1> /sbin/ldconfig -p | grep
boost_system | cut -d\> -f2
 /usr/lib64/libboost_system.so.1.66.0
-----------[END SESSION]-----------

According to YaST, libboost_system and libboost_thread are installed.

My system details are:
  OS: openSUSE Leap 15.3
  PC: Lenovo Ideapad Slim 7
  CPU: Intel Core i7

Does anyone know what the problem is here?


Post a reply to this message

From: Cousin Ricky
Subject: Re: C compiler cannot create executables
Date: 6 Sep 2021 23:35:00
Message: <web.6136dd40362afd1260e0cc3d949c357d@news.povray.org>
ricky@localhost:/usr/lib64> ls -l libboost*
-rwxr-xr-x 1 root root  72312 Jun  5  2020 libboost_date_time.so.1.66.0
-rwxr-xr-x 1 root root  93464 Jun  5  2020 libboost_filesystem.so.1.66.0
-rwxr-xr-x 1 root root 109824 Jun  5  2020 libboost_iostreams.so.1.66.0
-rwxr-xr-x 1 root root 970816 Jun  5  2020 libboost_locale.so.1.66.0
-rwxr-xr-x 1 root root  18736 Jun  5  2020 libboost_system.so.1.66.0
-rwxr-xr-x 1 root root 175584 Jun  5  2020 libboost_thread.so.1.66.0


Post a reply to this message

From: Cousin Ricky
Subject: Re: C compiler cannot create executables
Date: 7 Sep 2021 00:50:00
Message: <web.6136ef56362afd1260e0cc3d949c357d@news.povray.org>
"Cousin Ricky" <rickysttATyahooDOTcom> wrote:
> I just got a new computer, and due to library incompatibilities, I have to
> recompile all my POV 3.7 and up executables.  The configure stage halts with
> this message:
>
> [snip]
> checking for gcc... gcc
> checking whether the C compiler works... no
> configure: error: in `/home/ricky/povray/povunix-v3.8.0-beta.2-src':
> configure: error: C compiler cannot create executables
> See `config.log' for more details

OK, I'm beginning to see what's going on here.  It's the same problem I had 3
years ago, only much deeper.  It seems openSUSE is deleting more and more
development tools with each upgrade.  (The latest didn't even come with a C/C++
compiler!)


Post a reply to this message

From: Thorsten
Subject: Re: C compiler cannot create executables
Date: 7 Sep 2021 11:24:56
Message: <61378448$1@news.povray.org>
On 07.09.2021 06:49, Cousin Ricky wrote:
> "Cousin Ricky" <rickysttATyahooDOTcom> wrote:
>> I just got a new computer, and due to library incompatibilities, I have to
>> recompile all my POV 3.7 and up executables.  The configure stage halts with
>> this message:
>>
>> [snip]
>> checking for gcc... gcc
>> checking whether the C compiler works... no
>> configure: error: in `/home/ricky/povray/povunix-v3.8.0-beta.2-src':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details
> 
> OK, I'm beginning to see what's going on here.  It's the same problem I had 3
> years ago, only much deeper.  It seems openSUSE is deleting more and more
> development tools with each upgrade.  (The latest didn't even come with a C/C++
> compiler!)

That is actually pretty common these days. In many production systems, 
you do not (really) need a compiler because the admin will have one on 
his system and distribute what is needed via the package management 
and/or other deployment tools.

Compilers and the development libraries do consume a real lot of space 
these days, and all they add is a tool that would in many cases only 
help an intruder (not the compiler, but lots of the other dev tools, 
like the debugger) on the spot. So there is a security aspect to it, too.

Thorsten


Post a reply to this message

From: Cousin Ricky
Subject: Re: C compiler cannot create executables
Date: 7 Sep 2021 16:45:00
Message: <web.6137cf40362afd1260e0cc3d949c357d@news.povray.org>
Thorsten <tho### [at] trfde> wrote:
> On 07.09.2021 06:49, Cousin Ricky wrote:
> >
> > OK, I'm beginning to see what's going on here.  It's the same problem I had 3
> > years ago, only much deeper.  It seems openSUSE is deleting more and more
> > development tools with each upgrade.  (The latest didn't even come with a C/C++
> > compiler!)
>
> That is actually pretty common these days. In many production systems,
> you do not (really) need a compiler because the admin will have one on
> his system and distribute what is needed via the package management
> and/or other deployment tools.

That was my thought as well, except I was thinking in terms of fitting the OS on
a DVD, rather than security.

> Compilers and the development libraries do consume a real lot of space
> these days, and all they add is a tool that would in many cases only
> help an intruder (not the compiler, but lots of the other dev tools,
> like the debugger) on the spot. So there is a security aspect to it, too.


Post a reply to this message

Copyright 2003-2021 Persistence of Vision Raytracer Pty. Ltd.