24 May
2007
24 May
'07
10:36 p.m.
On Thu, 2007-05-24 at 16:28 -0700, Ken Restivo wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, May 23, 2007 at 03:25:26PM -0400, Paul Davis wrote:
thats a bug in checkinstall. if you run scons install, that will not
happen.
On Wed, 2007-05-23 at 12:14 -0700, Ken Restivo
wrote:
No need to shout. I was claiming it because it was in fact happening. It may be a bug in
checkinstall though, and not in scons or in your build. But it's definitely there:
$ cd ardour-2.0.2
$ checkinstall
<answer prompts to build package>
$ dpkg-deb -c ../ardour_2.0.2-1_amd64.deb
- -rw-r--r-- root/root 114 2007-05-06 21:39 ./usr/share/doc/ardour/README
- -rw-r--r-- root/root 17992 2007-05-06 21:39 ./usr/share/doc/ardour/COPYING
- -rw-r--r-- root/root 546 2007-05-06 21:39 ./usr/share/doc/ardour/PACKAGER_README
drwxr-xr-x root/root 0 2007-05-19 17:09 ./usr/bin/
lrwxrwxrwx root/root 0 2007-05-19 17:09 ./usr/bin/gcc -> gcc-4.1
lrwxrwxrwx root/root 0 2007-05-19 17:09 ./usr/bin/g++ -> g++-4.1
Weird. That's what I had to do in order to get
Ardour2 going, since the Debian package uses SYSLIBS=1 and thusly makes it non-functional
on my machine.
I tried checkinstall too, but that had issues: apparently the Ardour2 scons target tries
to make symlinks for /usr/bin/gcc, and dpkg rightly refused to allow it to something so
dangerous.
THIS IS NOT TRUE.
its also the 2nd time that its been claimed. please either point to the
line in our scons build system where this happens, or stop claiming that
it does. I still think that The Right Thing would be to find
and fix the problem with the system libs, rather than just bypassing them. But if
SYSLIBS=0 works, then that's probably good enough. FYI, I'm pretty sure that the
ardour 0.99 package used the system libs, and worked fine.
its not a problem with the system libs. its a problem when some
unknowing user, for whatever reason, installs a new version of g++ and
rebuilds either ardour or the affected libraries, but not both. bizarre
behaviour ensues, we waste hours or days tracking it down, only to find
that its another problem with mismatching g++ issues. it doesn't even
need that - at least one distro built some of its c++ libraries so that
they didn't use exceptions, which then breaks other c++ code.
we dealt with this years ago by deciding to include every c++ library
that ardour uses in the source tree, except those that actually come
with the compiler.
we did not sanction the use of SYSLIBS=1 for ardour 0.99.3, and we will
not sanction it for any version in the future.
--p