|
 |
On 08/26/2017 03:10 AM, LanuHum wrote:
> Hi!
> My newest Cygwin64 is wrong in the configuration. :(
>
>
I'm not a cygwin user, but the fail looks to happen with the most basic
g++ test of the linker. Specifically:
g++: fatal error: -fuse-linker-plugin, but cyglto_plugin.dll not found
If you search your system, does the dll exist? If so, does the version
look to match the gcc,g++ versions you are using? If not, ... maybe, can
you get a cygwin version which isn't configured to use lto or use g++
flags during configure to disable the lto feature?
I think the issue here - likely - is the lto dll isn't properly set up
in your new cygwin64 install. When I tried lto with Ubuntu linux some
time back, I had to specifically install other packages to get the lto
support working maybe something similar must be done in the cygwin
environments?
Aside 1: A question I've been carrying around in my head for my Ubuntu
lto experiments is whether some sort of 'more static' link is required
to see much benefit because I've seen little in my experiments. To this
end it is interesting for me to see these flags in your post:
...
--enable-shared --enable-shared-libgcc --enable-static
...
which looks like, perhaps, some dynamic/static mixed linking is being
done. My novice attempts at such mixed static for all but libsdl
linking all failed...
Aside2: On Ubuntu static links of libsdl don't work so you get no
preview display, but POV-Ray runs. The first issue here looks to be how
libsdl was set up to link. After which, there are issues in debian based
linux-es not shipping some of the .a archives on which sdl1.2 depends -
making it impossible to statically link it without rebuilding those
libraries with the needed archives...
Another thought. Have you tried a simple "hello world" compile and link
in the cygwin environment? I expect this too will fail and it would be
simpler to use that as the test vehicle to figure things out - asking
about that fail in cygwin support fora you can find.
Bill P.
Post a reply to this message
|
|
