From: Douglas McGilvray <d.mcgilvray@el...> - 2004-11-10 18:24:29
We have a fix for the -fno-exceptions / -fexceptions problem:
The -fexceptions flag is set in USE_EXCEPTIONS. This needs to be added to
CXXFLAGS to cancel out the -fno-exceptions. The configure script which is
shipped with RG seems to have a fix for this already, but, because the fix is
in the generated script it is lost as soon as automake is run.
To fix, add this line after KDE_CHECK_COMPILER_FLAG(fexceptions ......
This makes the current solution permanent. Alternatively, 'fexceptions' is
enabled by default in g++ (
fexceptions is required for any c++ which uses exception handling - and also
needed for linking with QT. So is it worth taking both these flags out
RG compiles fine with either solution - at least until the next problem...
undefined reference to `VTT for RosegardenSequencerApp'
undefined reference to `vtable for Rosegarden::MidiFile' etc..............
Still no joy with this one yet unfortunately. Any ideas appreciated.
From: Nicholas Bailey <n.bailey@el...> - 2004-11-11 10:21:58
-----BEGIN PGP SIGNED MESSAGE-----
To add to doug's post, I notice that the Seqencer and Sound directories
are for some reason building their libraries in the same place
(sequencer/.libs or sound/.libs, can't remember which, but not both).
Also, one of them is an archive (.a) and the other a shared object
Is this a conspiracy or a cockup? :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
-----END PGP SIGNATURE-----
From: Chris Cannam <cannam@al...> - 2004-11-11 10:29:22
On Thursday 11 Nov 2004 10:21, Nicholas Bailey wrote:
> To add to doug's post, I notice that the Seqencer and Sound
> directories are for some reason building their libraries in the same
> place (sequencer/.libs or sound/.libs, can't remember which, but not
> Also, one of them is an archive (.a) and the other a shared
> object (.so).
sound/.libs, and sequencer is the one with the .so.
> Is this a conspiracy or a cockup? :)
A cockup. There's actually no reason for sequencer to build a library
at all, let alone a shared one that actually gets installed. All
the .o's in libRosegardenSequencer.so really should just be linked into
It might be worth your time looking at scripts/simple-makefile, which
does a build without using libtool and without creating a .so for the
sequencer. It might help clarify which bits of all the libtool
nonsense are actually doing useful things, and which are just there
because they turned up one day and we never noticed or hadn't the time
or competence to work out how to get rid of them.