Hi David,
Am Samstag, 21. Januar 2006 06:36 schrieb David Reiser:
> Has something changed in the build system, or have I screwed
> something else up?:
something has changed in the build system. Martin has introduced the
-fvisibility=hidden argument into all qt-related source code as well. We/he
might easily have forgotten to correctly mark one symbol or the other as
non-hidden.
Oh. I just got the very same linker errors on suse9.3 / gcc3.3.5, which means
-fvisibility=hidden isn't used, but the build system has been changed
nevertheless. We'll look into that.
BTW which gcc do you have? If this is gcc3.x then this argument is not used
anyway. If you have gcc4.x, then this is by default enabled; as a workaround
you can force it disabled on your platform by changing configure.ac line 964
from
0.* | 1.* | 2.* | 3.*)
into
0.* | 1.* | 2.* | 3.* | 4.* )
and rebuild everything. I know that Martin is still working on that area, so
you might want to wait a few days until you start to use that feature on Mac
OSX as well. But as I said I just saw the very same linker errors on
gcc3.3.5.
Christian
>
> attempting to build 1.9.2.3cvs, I get
>
> ld: Undefined symbols:
> __ZN10QBCfgTabUi11qt_propertyEiiP8QVariant
> __ZN10QBCfgTabUi16staticMetaObjectEv
> __ZN10QBCfgTabUi7qt_castEPKc
> __ZN10QBCfgTabUi7qt_emitEiP8QUObject
> __ZN10QBCfgTabUi9qt_invokeEiP8QUObject
> __ZTI10QBCfgTabUi
> __ZN10QBCfgTabUi2trEPKcS1_
> __ZTV10QBCfgTabUi
> /usr/bin/libtool: internal link edit command failed
> make[7]: *** [libqbanking.la] Error 1
>
> I should never be trying to use /usr/bin/libtool, since Apple's
> libtool is no relation to gnu libtool (and if I move /usr/bin/libtool
> out of the way, the build system complains about not being able to
> find ranlib).
>
> If I do 'which libtool' immediately after the error, I get '/sw/bin/
> libtool', which is at least a symlink to a gnu libtool. But I would
> think I ought to be going to the libtool in my build directory,
> shouldn't I?
>
> What makes this really annoying is that I had a similar error
> Wednesday night (really 2am Thursday), and I found some way around it
> -- successfully building 1.9.1.2cvs. At this point I don't know if
> that's a solid build, but it did complete. But I cannot remember what
> I did then to get around the problem.
>
> I'll keep working on this, but I am hoping someone recognizes
> something obvious.
> --
> David Reiser
> [EMAIL PROTECTED]
> Mac 10.4.4, gcc 4.0.1
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Aqbanking-devel mailing list
> Aqbanking-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/aqbanking-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Aqbanking-devel mailing list
Aqbanking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aqbanking-devel
