From alex at pressure.to Wed Oct 19 04:24:56 2011
From: alex at pressure.to (Alex Fenton)
Date: Wed, 19 Oct 2011 09:24:56 +0100
Subject: [wxruby-development] [wxruby-users] Packaging wxRuby fails
In-Reply-To: <4E88CC7B.5050000@pressure.to>
References: <4D779EDD.4090806@gmx.net> <103535ecce64256f7c8307c1fc5ccf1b@ruby-forum.com> <4DA160CE.30101@gmx.net> <4DC817F5.4050405@gmx.net>
<4DC8480C.4090200@pressure.to> <4DC97389.4080709@gmx.net>
<4E88CC7B.5050000@pressure.to>
Message-ID: <4E9E8958.4070905@pressure.to>
hello all - have now committed this patch - looks excellent and works
fine on my main Ubuntu box (11.10). Thanks again and sorry to be slow -
have just started a new job and moved hosts.
We should look to release a bug-fix 2.0.2 soon - I have a little bit of
time this weekend. There are some uncommitted patches I'd like to review
at http://rubyforge.org/tracker/?atid=220&group_id=35&func=browse
We had thought that we wouldn't add features to 2.0.x line, but I'd
favour merging these given our slow (!) release schedule. Discussion
welcome (preferably on wxruby-dev).
best
alex
On 02/10/11 21:41, Alex Fenton wrote:
> hi
>
> thanks very much for the research, summary and patch. I've just got
> back from holiday, but will have a look at this later this week with a
> view to merging. I'm using 11.04 so should be able to test directly.
>
> best alex
>
> On 01/10/11 10:22, David Beswick wrote:
>> Hi everyone, an update on this problem and wxruby's gem and build
>> troubles. I was just able to build wxruby and run bigdemo with the
>> help of a propose d natty (11.04) fix for Ubuntu's apt wxwidgets
>> package. This is great progress! As soon as the natty fix is
>> released, binary gems might be ready to go again.
>>
>> To summarise the problems and their fixes so far:
>>
>> 1. Previously, running any wxruby app would cause a crash in pixman.
>> This has possibly been narrowed down to a problem with mesa or opengl
>> drivers and it affects many projects that link dynamically to
>> wxwidgets as well as other gui toolkits. Excluding opengl support
>> seems to fix this for wxruby. See
>> https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/756237
>>
>> 2. An additional problem cropped up in Natty, and maybe other
>> versions. The Xinerama library is in an unusual place in Ubuntu
>> 64-bit. wxwidget's configure script can't find it and so it disables
>> support for the wxDisplay class (as if --disable-display was given,)
>> and this causes rake compile to fail because there's no definition of
>> wxDisplay::ResetMode. There is an official proposed fix for this now,
>> see
>> https://bugs.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/828999,
>> and follow the directions to get the fixed package. Please take a
>> moment to verify the fix on the bug page, if you try it.
>>
>> 3. Just today, I discovered a problem with the wxruby rake files. The
>> rake files exclude various classes from the build on linux, but the
>> logic fails because code reads the array $excluded_classes in
>> rakeunixish.rb before the array is actually set up at the bottom of
>> rakeconfigure.rb. This causes link to fail because libgtk-media isn't
>> present, and MediaCtrl should be excluded from the build. I added a
>> class to wrap the functionality of extracting and testing for wx
>> features, and it's implemented such that querying wx features should
>> be insensitive to the order of different bits of code. Please apply
>> the attached patch to fix this, let me know if you have problems with it.
>>
>>
>>
>> On Wed, May 11, 2011 at 3:19 AM, Quintus > > wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Am 09.05.2011 22:01, schrieb Alex Fenton:
>> > On 09/05/11 17:36, Quintus wrote:
>> >> Some progress seems to have been made, but wxRuby still
>> doesn't run on
>> >> any Ubuntu> Lucid. The bug at
>> >>
>> https://bugs.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/632984 has
>> >> finally been fixed (for Oneiric), just to reveal another one
>> (see my
>> >> last comment on that bug) that still prevents the main bug at
>> >> https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/756237
>> to get
>> >> flagged for Natty.
>> >
>> > thanks for the update - and thanks also for reporting on and
>> documenting
>> > the issues on the Ubuntu bugtracker. I was half-thinking of
>> switching to
>> > Fedora anyway before the next Ubuntu came out - maybe this will
>> tip me
>> > over.
>>
>> I think I already mentioned it, but it was exaktly wxRuby that
>> was the
>> final reason for me to switch from Ubuntu to Arch Linux. I really
>> enjoy
>> the rolling release model now--no way back. :-)
>>
>> However, Ubuntu is the most-widespread Linux distribution out there.
>> It's not wise to drop support for it I think, because it would
>> significantly state a contrast to the platform-indepentness
>> wxRuby aims
>> to provide.
>>
>> > Martin, I have been quite successful at deploying both 32 bit and
>> > 64-bit
>> > 10.04 installations of wxRuby. I had to go back to the 2.0.0
>> gem for
>> > 64, but
>> > it seems to work quite fine with our rather elaborate application.
>>
>> Ubuntu Lucid 64bit worked without a problem for me, even though I
>> had to
>> compile wxRuby 2.0.1 myself. It's just that wxRuby doesn't work
>> on each
>> and every Ubuntu *after* Lucid.
>>
>> And btw. my name is Marvin, note the v. :-)
>>
>> > Hi Don, on which distributions and versions of those distributions
>> > were you
>> > deploying your apps on?
>>
>> I can confirm wxRuby not working for Ubuntu Maverick 64bit, Ubuntu
>> Maverick 32bit, Ubuntu Natty 32bit (the last to being virtual
>> machines)
>> and Arch Linux 64bit (completely updated last Friday)*. But I
>> suppose it
>> doesn't work for different reasons on each machine... :-(
>>
>> > Here's the bug that discussion references, in Debian:
>> >
>> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613221
>>
>> Thanks! It really looks like a bug in pixman then.
>>
>> ###########################
>>
>> So, what can we do now? wxRuby's obviously not at fault, it's
>>
>> a) pixman that is broken and
>> b) Debian/Ubuntu that ships broken wxWidgets packages
>>
>> b) is marked as fixed for Oneiric, but I doubt wheather wxRuby
>> will run
>> then, because of a) and a symbol lookup error I already described on
>> Launchpad (this would be c) then I think).
>>
>> The pixman bug breaks wxRuby on nearly every recent Linux
>> distribution,
>> and Debian/Ubuntu breaks it a second time due to their package
>> management, which is especially problementic because of their
>> popularity.
>>
>> To conclude: I'm worried about wxRuby's future, although it seems
>> that
>> wxRuby can't do much about the mentioned problems.
>>
>> > best
>> > alex
>>
>> Valete,
>> Marvin
>>
>> * The distros I were using "normally", i.e. not as virtual machines,
>> were like this:
>> Ubuntu Lucid 64bit -> Ubuntu Maverick 64bit [broke wxRuby] ->
>> Arch Linux
>> 64bit
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQEcBAEBAgAGBQJNyXOBAAoJELh1XLHFkqhajpYIAK0/ZBrho5fd9fGaEkGGQbal
>> +uwRxdavIldM38I8wolfIomPEZxTzupim+NPLigB1NHToUrSjhhCGkg482YuJR9u
>> HMncfRInw5eK/rXo1xHwF213sY3bZtxy9EOG+lJ/qLCm6qrke5tAGBKLzsY62QtG
>> v4KOXGNOyC+NEtdHFyPhancvwqrjfnyL/OjgUMku03saLq58vDZMiv1rAz++m69c
>> RO5h6sIZ+ZHp4tVIKSMKjLYoyQrVfuNK/A0RJMdpnLlsz+oAiP36sS65wKEL1wB4
>> +F62p7Ow/yjgItqAeG2HgKRcJyKwRT9tXSK8M83dsxWk9hyJVubILa2dWpvsD70=
>> =12Su
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> wxruby-users mailing list
>> wxruby-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/wxruby-users
>>
>>
>>
>> _______________________________________________
>> wxruby-users mailing list
>> wxruby-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/wxruby-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: