Building 0.44 on Debian (Was: Re: 0.44 Release tarball)
On 6/23/06, Terry Hancock <hancock@...1624...> wrote:
Michael Moore wrote:
I got it to build on Ubuntu 6.06 following the instructions at http://inkscape.org/wiki/index.php/CompilingUbuntu It took FOREVER to compile, well, 20-30 minutes. Far longer than the other non-trivial code that I've compiled, such as Vim. Is this normal?
Did use the instructions with "apt-get build-dep inkscape" ?
As I posted earlier, this might work with Ubuntu, but it does not work with Debian proper. At this time you get:
I didn't touch the Debian compiling wiki page, but looks like someone else had the same idea. It did work for Ubuntu though.
Building Dependency Tree... Done E: Build-dependencies for inkscape could not be satisfied.
By Debian proper do you mean Sarge or Etch? Are all updates applied? I might be able to look into this.
I suspect this is due to a package conflict in one of your deps, though I haven't figured out how to get apt to tell me exactly what the problem is.
Yeah, that sounds right. Which repositories do you have enabled? I'm not sure if Debian has the same terminology, but I have my Ubuntu looking in main, Universe and Multiverse. If the Debian box is just looking in main and Inkscape requires something in Universe (or equivalent) that may be why.
Thanks,
Michael Moore wrote:
On 6/23/06, Terry Hancock <hancock@...1624...> wrote:
Building Dependency Tree... Done E: Build-dependencies for inkscape could not be satisfied.
By Debian proper do you mean Sarge or Etch? Are all updates applied? I might be able to look into this.
I suspect this is due to a package conflict in one of your deps, though I haven't figured out how to get apt to tell me exactly what the problem is.
Yeah, that sounds right. Which repositories do you have enabled? I'm not sure if Debian has the same terminology, but I have my Ubuntu looking in main, Universe and Multiverse. If the Debian box is just looking in main and Inkscape requires something in Universe (or equivalent) that may be why.
Debian doesn't use the same terminology.
If there are missing deps, I'd put my money on liblcms or libsigc++.
Aaron Spike
Aaron Spike wrote:
Michael Moore wrote:
On 6/23/06, Terry Hancock <hancock@...1624...> wrote:
Building Dependency Tree... Done E: Build-dependencies for inkscape could not be satisfied.
By Debian proper do you mean Sarge or Etch? Are all updates applied? I might be able to look into this.
Well, I haven't used the 'build-dep' command much, but assuming that -t works for build-dep like it does for 'install', then *both* (and Sid, too), I tried 'stable'='Sarge', 'testing'='Etch', and 'unstable'='Sid'.
I suspect this is due to a package conflict in one of your deps, though I haven't figured out how to get apt to tell me exactly what the problem is.
Yeah, that sounds right. Which repositories do you have enabled? I'm not sure if Debian has the same terminology, but I have my Ubuntu looking in main, Universe and Multiverse. If the Debian box is just looking in main and Inkscape requires something in Universe (or equivalent) that may be why.
Debian doesn't use the same terminology.
Apparently not, because I have no idea what he's talking about. ;-)
Debian has 'main', 'contrib', and 'non-free'. I suspect Debian's 'main' is much larger than Ubuntu's (unless they refer to the same thing), because it is truly vast (I think Etch takes 15 CDs). I think I also have one or two non-standard repositories (Cairo, I think), but I doubt that an extra repository would cause the problem.
If there are missing deps, I'd put my money on liblcms or libsigc++.
IMHO, it's not likely a question of missing deps, but more likely missing/incompatible *versions* of deps. Especially since 0.43 is part of Debian main (are there a lot of new deps in 0.44, or just new versions? -- I would expect the latter).
OTOH, running 'ldd inkscape' on the new binary just floored me. Man, what a lot of shared libraries! I guess that's normal for a big graphics application.
Actually, I did get *some* feedback though. Let me try this again ...
I was following this: http://wiki.inkscape.org/wiki/index.php/CompilingDebian
After the 'build-dep' instructions (which failed uninformatively), there's 'another method', in which they get the deps from debian/control and just try to install, so let's try that:
apt-get --simulate install debhelper intltool libart-2.0-dev libgc-dev libglib2.0-dev libgnomevfs2-dev libgtk2.0-dev libglibmm-2.4-dev libgtkmm-2.4-dev libgtkspell-dev libpango1.0-dev libpng12-dev libpopt-dev libsigc++-2.0-dev libtool libxml-parser-perl libxml2-dev libxslt1-dev pkg-config zlib1g-dev liblcms1-dev
(watch out for line-wrap)
[... omitted some output from apt-get ...]
The following information may help to resolve the situation: The following packages have unmet dependencies: libglib2.0-dev: Depends: libglib2.0-0 (= 2.10.3-1) but 2.8.6-1 is to be installed libgnomevfs2-dev: Depends: libgconf2-dev (>= 2.8.0-1) but it is not going to be installed libgtk2.0-dev: Depends: libgtk2.0-0 (= 2.6.4-3.1) but 2.8.13-1 is to be installed Depends: libatk1.0-dev (>= 1.6.1-2) but it is not going to be installed libpango1.0-dev: Depends: libpango1.0-0 (= 1.8.1-1) but 1.10.4-1 is to be installed
For thoroughness, try with different target dist versions:
'-t stable' gives me: [...] The following packages have unmet dependencies: libglib2.0-dev: Depends: libglib2.0-0 (= 2.10.3-1) but 2.8.6-1 is to be installed libgnomevfs2-dev: Depends: libgconf2-dev (>= 2.8.0-1) but it is not going to be installed libgtk2.0-dev: Depends: libgtk2.0-0 (= 2.6.4-3.1) but 2.8.13-1 is to be installed Depends: libatk1.0-dev (>= 1.6.1-2) but it is not going to be installed libpango1.0-dev: Depends: libpango1.0-0 (= 1.8.1-1) but 1.10.4-1 is to be installed E: Broken packages
'-t testing' gives me: [...] The following packages have unmet dependencies: libgtk2.0-dev: Depends: libgtk2.0-0 (= 2.8.18-1) but 2.8.13-1 is to be installed Depends: libxinerama-dev but it is not going to be installed Depends: libxcursor-dev but it is not going to be installed Depends: libxfixes-dev but it is not going to be installed libgtkmm-2.4-dev: Depends: libgtkmm-2.4-1c2a (= 1:2.8.8-1) but it is not going to be installed libgtkspell-dev: Depends: libgtkspell0 (= 2.0.10-3+b1) but 2.0.10-1 is to be installed libpango1.0-dev: Depends: libxft-dev but it is not going to be installed E: Broken packages
'-t unstable' gives me: [...] The following packages have unmet dependencies: libgtk2.0-dev: Depends: libgtk2.0-0 (= 2.8.18-1) but 2.8.13-1 is to be installed Depends: libxinerama-dev but it is not going to be installed Depends: libxcursor-dev but it is not going to be installed Depends: libxfixes-dev but it is not going to be installed libgtkmm-2.4-dev: Depends: libgtkmm-2.4-1c2a (= 1:2.8.8-1) but it is not going to be installed libgtkspell-dev: Depends: libgtkspell0 (= 2.0.10-3+b1) but 2.0.10-1 is to be i nstalled libpango1.0-dev: Depends: libxft-dev but it is not going to be installed E: Broken packages
I'm guessing that this is more-or-less the problem that 'apt-get build-dep inkscape' must be running into (or actually a different problem on stable and testing?)
IIRC, I spent a little time trying to tease libglib and libgtk to install consistent versions, but it seemed like the -dev and the runtime versions didn't agree with each other (note the '=' version dependency). I don't remember exactly what I tried, but nothing I tried worked.
I'm sure this is actually a Debian problem, and not Inkscape's, but you probably ought to know about it.
BTW, this is academic for my sake -- I got the RPM binary to install using alien, which is all I really wanted. I'm sure that the Debian maintainer of Inkscape will get around to packaging 0.44 in time, and I don't have a compelling desire to install it from source on principle (I just wanted to use it).
But I'm hoping it's helpful to others.
Cheers, Terry
participants (3)
-
Aaron Spike -
Michael Moore -
Terry Hancock