Unexpected gcc linking behavior on -CURRENT

[Alexander Leidinger]

Quoting Matt <datahead4 at gmail.com> (Fri, 21 Sep 2007 13:36:24 -0500):

> Hello all.
> 
> I've been working on getting VirtualBox to build on -CURRENT and have
> hit what I think might be a compiler snag based on the error and some
> of the mails I've seen to the freebsd-java mailing list over the last
> months.
> 
> Any insights into how to isolate and hopefully correct this error
> would be greatly appreciated.  The code builds cleanly on a
> 6.2-RELEASE box using gcc 3.4.6.  The error on -CURRENT (from 9/13)
> using gcc 4.2.1 is as follows:
> 
> kBuild: Linking
> VBoxSVCout/freebsd.x86/release/obj/src/VBox/Main/VBoxSVC/linux/server.o(.text+0x313):
> In function `__static_initialization_and_destruction_0':
> src/VBox/Main/linux/server.cpp:594: undefined reference to `_292'
> out/freebsd.x86/release/obj/src/VBox/Main/VBoxSVC/linux/server.o(.text+0x31d):src/VBox/Main/linux/server.cpp:594:
> undefined reference to `_292'

I've seen something like this because of compiler bugs depending on the
optimization level. Try different optimization levels and have a look
what happens (complete rebuild of the source in question).

Bye,
Alexander.

-- 
Graduate life -- it's not just a job, it's an indenture.
http://www.Leidinger.net  Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org     netchild @ FreeBSD.org  : PGP ID = 72077137