Report for 2004-07-18 18:00 GMT-0500
Hi. I have some bad news.
Unfortunately, the last build attempt at compiling Inkscape CVS was very unsuccesful.
I'm sorry, I really tried hard. Really.
Here is the LOG file, and I hope that helps.
On Sun, 2004-07-18 at 19:00, inkscape@...382... wrote:
Hi. I have some bad news.
Unfortunately, the last build attempt at compiling Inkscape CVS was very unsuccesful.
...
Requested 'gtk+-2.0 >= 2.4.0' but version of GTK+ is 2.2.4
Unsurprisingly, you need to install gtk+ 2.4. You will also need sigc++ 2.0 and gtkmm 2.4.
Note that we wil also be adding a dependency on libgc soon.
(am I replying to an automated email? the text sounds familiar..)
-mental
Hello.
On Sun, 2004-07-18 at 22:22, MenTaLguY wrote:
On Sun, 2004-07-18 at 19:00, inkscape@...382... wrote:
Hi. I have some bad news.
Unfortunately, the last build attempt at compiling Inkscape CVS was very unsuccesful.
...
Requested 'gtk+-2.0 >= 2.4.0' but version of GTK+ is 2.2.4
Unsurprisingly, you need to install gtk+ 2.4. You will also need sigc++ 2.0 and gtkmm 2.4.
Note that we wil also be adding a dependency on libgc soon. (am I replying to an automated email? the text sounds familiar..) -mental
Youp. It's one step in the autobuilding process. Yet since SourceForge decided to block all posts originated from DSL-based SMTP servers, the reports were forgotten (which was kind of fine). I don't know how this went through. I'm taking inkscape-devel out of the reporting list, however. If anyone is interested in receiving those automated reports, just let me know.
On other news, I'm afraid the Bleeding-Edge Inkscape Factory will shut (some of) its doors after the recent upgrade to gtk-2.4. I'm running some kind of Mandrake 9.15 (while upgrading to MDK92 the disk ran out of space...), so RPM is gone and upgrading packages is an enduring entertainment (if you are insane, that is). So, the Linux part I guess will be buried. (If I had a sane Mandrake installation, I could autobuild RPM's as well. Oh well...)
The Win32 autobuild I suppose will have no problems, but I don't know the status for that.
Greetings.
Daniel Díaz yosoy@...31...
Mike Hearn is in the same boat with the autopackage builds.
Since the codebase can be expected to be in flux with new development, it is okay for the nightly builds to be temporarily unavailable.
Bryce
On Mon, 19 Jul 2004, Daniel [ISO-8859-1] D�az wrote:
On other news, I'm afraid the Bleeding-Edge Inkscape Factory will shut (some of) its doors after the recent upgrade to gtk-2.4. I'm running some kind of Mandrake 9.15 (while upgrading to MDK92 the disk ran out of space...), so RPM is gone and upgrading packages is an enduring entertainment (if you are insane, that is). So, the Linux part I guess will be buried. (If I had a sane Mandrake installation, I could autobuild RPM's as well. Oh well...)
The Win32 autobuild I suppose will have no problems, but I don't know the status for that.
Greetings.
Daniel D�az yosoy@...31...
MenTaLguY wrote:
On Sun, 2004-07-18 at 19:00, inkscape@...382... wrote:
Hi. I have some bad news.
Unfortunately, the last build attempt at compiling Inkscape CVS was very unsuccesful.
...
Requested 'gtk+-2.0 >= 2.4.0' but version of GTK+ is 2.2.4
Unsurprisingly, you need to install gtk+ 2.4. You will also need sigc++ 2.0 and gtkmm 2.4.
Note that we wil also be adding a dependency on libgc soon.
(am I replying to an automated email? the text sounds familiar..)
-mental
One possibility, is that we can build sigc++/glibmm/gtkmm with ./configure --enable-static , so that we can link statically with those, and not require the end-user to have them.
Bob
participants (6)
-
unknown＠example.com -
Bob Jamison -
Bryce Harrington -
Daniel Díaz -
Kees Cook -
MenTaLguY