Re: [Inkscape-devel] Inkscape 0.42 pre 3
Lucas Vieites wrote:
El vie, 22-07-2005 a las 08:57 -0500, aaron@...749... escribió:
Ted Gould wrote:
Binaries will start appearing shortly, please check back if you're using binary releases of Inkscape.
http://inkscape.modevia.com/ap/inkscape-0.41+0.42pre3.x86.package
Hi, I just installed this package an when I run inkscape I get the following output and a core dump: Notes: -libpng12.so.0 is available at /usr/lib/libpng12.so.0 -if I try to run inkscape more than once the preferences.xml file gets truncated and it issues an error for that also.
$ inkscape inkscape: /usr/bin/../lib/libpng12.so.0: no version information available (required by inkscape) art_render_invoke: no image source given
Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Segmentation fault (core dumped)
Is this enough to file a bug?
What distribution are you using? My guess is that you are using Debian Unstable and that this crash is caused by the currently inprogress switchover to gcc 4.0.
I suppose after this all settles down we might need packages build with gcc 3.3 and pacakges build with gcc 4.0. Is this a correct assumption?
Aaron Spike
Aaron Spike
El vie, 22-07-2005 a las 11:30 -0500, aaron@...749... escribió:
Lucas Vieites wrote:
El vie, 22-07-2005 a las 08:57 -0500, aaron@...749... escribió:
[...]
Segmentation fault (core dumped)
Is this enough to file a bug?
What distribution are you using? My guess is that you are using Debian Unstable and that this crash is caused by the currently inprogress switchover to gcc 4.0.
I should've mentioned. Right now I'm running Mandriva 2005 LE (formerly Mandrake), and I don't have the slightest idea of what gcc version they used for it.
I suppose after this all settles down we might need packages build with gcc 3.3 and pacakges build with gcc 4.0. Is this a correct assumption?
Aaron Spike
Aaron Spike
Lucas Vieites wrote:
El vie, 22-07-2005 a las 11:30 -0500, aaron@...749... escribió:
Lucas Vieites wrote:
El vie, 22-07-2005 a las 08:57 -0500, aaron@...749... escribió:
[...]
Segmentation fault (core dumped)
Is this enough to file a bug?
What distribution are you using? My guess is that you are using Debian Unstable and that this crash is caused by the currently inprogress switchover to gcc 4.0.
I should've mentioned. Right now I'm running Mandriva 2005 LE (formerly Mandrake), and I don't have the slightest idea of what gcc version they used for it.
******** you can simply run gcc --version to find out (and g++ --version)
I suppose after this all settles down we might need packages build with gcc 3.3 and pacakges build with gcc 4.0. Is this a correct assumption?
I think for maybe the next year that is the best approach - now, all pkgs to Debian Unstable have to use gcc-4.0 and Fedora 4 is on gcc-4.0. Most others are still on gcc-3.3.x
Aaron Spike
Aaron Spike
John Taber wrote:
I think for maybe the next year that is the best approach - now, all pkgs to Debian Unstable have to use gcc-4.0 and Fedora 4 is on gcc-4.0. Most others are still on gcc-3.3.x
That's why we use "static" builds. Link Inkscape with gtkmm, glibmm, any C++ lib statically. With a .a instead of a .so. Also, you can build gcc itself with --disable-shared, so that libstdc++ itself is a .a also. This avoids the C++ ABI incompatibilities. Straight C should be universally linkable. After building, you should do an 'ldd inkscape' to view its dependencies.
Bob
On Fri, 22 Jul 2005 11:30:35 -0500, aaron-XW8b5UTxoeLYtjvyW6yDsg wrote:
Lucas Vieites wrote:
$ inkscape inkscape: /usr/bin/../lib/libpng12.so.0: no version information available (required by inkscape)
You can ignore this.
art_render_invoke: no image source given
I'm guessing this is the source of the problem, or at least related.
Is this enough to file a bug?
Could you run it under a debugger and get a backtrace? Alternatively try "catchsegv inkscape" and copy/paste the output here.
Also, please send us the output of "ldd `which inkscape`"
I suppose after this all settles down we might need packages build with gcc 3.3 and pacakges build with gcc 4.0. Is this a correct assumption?
That should not be necessary, unless the dependencies of Inkscape changed while I wasn't looking. Regardless, the 1.2 release of autopackage will ensure the user always gets a binary of the right ABI. If this really is a C++ issue, then that should solve it.
thanks -mike
Mike Hearn wrote:
I suppose after this all settles down we might need packages build with gcc 3.3 and pacakges build with gcc 4.0. Is this a correct assumption?
That should not be necessary, unless the dependencies of Inkscape changed while I wasn't looking. Regardless, the 1.2 release of autopackage will ensure the user always gets a binary of the right ABI. If this really is a C++ issue, then that should solve it.
What is the ETA on autopackage 1.2?
Aaron Spike
On Sun, 24 Jul 2005 06:56:34 -0500, aaron-XW8b5UTxoeLYtjvyW6yDsg wrote:
What is the ETA on autopackage 1.2?
Good question! It won't be ready in time for this Inkscape release, perhaps another month or two? We still need to fully document the new C++ code, make it easier/more automatic, get more tested etc. But the bulk of the code is in CVS so we're on the downhill slope.
thanks -mike
participants (5)
-
unknown＠example.com -
Bob Jamison -
John Taber -
Lucas Vieites -
Mike Hearn