CompilingFedora

Fedora Core 2 for Inkscape 0.40CVS

After having the most up to date RPMs for FC2 from fedora updates, this is what I found for compiling Inkscape.

Well...after checking out a clean copy of the inkscape module, autogen.sh will not generate ltmain.sh, so I had to make a softlink to a copy of ltmain.sh, which was located here: /usr/share/libtools/ltmain.sh

So I ran:

  $ ln -s /usr/share/libtools/ltmain.sh ./

Then I ran:

  $ ./autogen.sh

Then to get all the makefiles, I ran:

  $ ./configure

Now need to have Boehm Garbage collector installed. Follow the Boehm Garbage Collector instructions on the CompilingInkscape page for this to work. After installed, then rerun:

  $ ./configure

For libsigc++2 currently you must download and install: http://sourceforge.net/project/showfiles.php?group_id=1970

Now you need gtkmm 2.4 and glibmm 2.4:

http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.4/

http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.4/

You need to ./configure; make; make install for libsigc++, glibmm 2.4 and gtkmm 2.4

Afterwards update your paths and all that and then run ./autogen.sh; ./configure; make; make install on the CVS version of inkscape...

I don't think /usr/local/lib is in /etc/ld.so.conf or /etc/ld.so.conf.d/*.conf by default on FC2... Fix that, then `export LD_LIBRARY_PATH=/usr/local/lib`, then run `ldconfig`, and try running `inkscape`. -- Jizzbug

This is what i get now:

 *** glibc detected *** free(): invalid pointer: 0x0832ce78 ***
 Emergency save activated!

-- Confabulator

Mandrake 10.2 b3 and 0.41 Static Builds

If I try to run either the .386 or .686 Static Builds of 0.41 on Mandrake 10.2 beta3, I get the above error:

 *** glibc detected *** free(): invalid pointer: 0x0959d210 ***

The "invalid pointer" is a different value for each one, but same error. I don't have the dependencies I need to compile from source. So, I guess I'll wait another few months before trying Inkscape. (I'm so anxious. As an ex-user of Sodipodi, I've been waiting for something that was a bit more user friendly).

  -- This is almost certainly a GCC bug (MikeHearn)