I have noticed problems with some of the demo
and samples.
However I still have version 2.4.0.3 with the
demo's. I also have the demo and samples of
2.4.0.6
Now should I first upgrade to 2.4.0.6 before
I report the problems. What is the best way
to do so on a Debian system?
--
Antoon Pardon
Antoon Pardon wrote:
I have noticed problems with some of the demo
and samples.However I still have version 2.4.0.3 with the
demo's. I also have the demo and samples of
2.4.0.6Now should I first upgrade to 2.4.0.6 before
I report the problems.
That would be prefereable as some things have been fixed since then. However 2.4.0.7 will be released soon so you may want to wait a bit more.
What is the best way
to do so on a Debian system?
Well, the best way I suppose is to get new versions of the official packages. but I don't maintain those. Any other Debian users have any suggestions?
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
I find the easiest way is to run alien on the your RPMs. The resultant deb
installs and runs fine on my boxen (stable, testing, testing + unstable).
On Fri, Mar 21, 2003 at 03:59:12PM -0800, Robin Dunn wrote:
>What is the best way
>to do so on a Debian system?
>Well, the best way I suppose is to get new versions of the official
packages. but I don't maintain those. Any other Debian users have any
suggestions?
--
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/
Charl P. Botha wrote:
On Fri, Mar 21, 2003 at 03:59:12PM -0800, Robin Dunn wrote:
What is the best way
to do so on a Debian system?Well, the best way I suppose is to get new versions of the official packages. but I don't maintain those. Any other Debian users have any suggestions?
I find the easiest way is to run alien on the your RPMs. The resultant deb
installs and runs fine on my boxen (stable, testing, testing + unstable).
I forgot about alien. Glad to hear that it works.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
No such luck here.
If I run alien, I get the following error message:
# alien wxPythonGTK-py2.2-2.4.0.7-1.i386.rpm
Package build failed. Here's the log:
dh_testdir
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
dpkg: unexpected output of `gcc --print-libgcc-file-name': `libgcc.a'
dpkg: compiler libgcc filename not understood: no gcc-lib part
dh_installdirs:
make: *** [binary-arch] Error 1
The offical package seems blocked at 2.4.0.3
I thought about starting from the source package and if that worked,
getting the 2.4.0.7 and see if I could make my own, but getting the
build-deps, stated I had to install some specific packages, but
installing those would force me further in the direction of unstable
than I'm confortable with.
So it seems I'm stuck.
On Sat, Mar 22, 2003 at 01:02:53AM +0100, Charl P. Botha wrote:
On Fri, Mar 21, 2003 at 03:59:12PM -0800, Robin Dunn wrote:
> >What is the best way
> >to do so on a Debian system?
> >
>
> Well, the best way I suppose is to get new versions of the official
> packages. but I don't maintain those. Any other Debian users have any
> suggestions?I find the easiest way is to run alien on the your RPMs. The resultant deb
installs and runs fine on my boxen (stable, testing, testing + unstable).
--
Antoon Pardon
> > >What is the best way
> > >to do so on a Debian system?
> > >
> >
> > Well, the best way I suppose is to get new versions of the official
> > packages. but I don't maintain those. Any other Debian users have any
> > suggestions?
>
> I find the easiest way is to run alien on the your RPMs. The resultant deb
> installs and runs fine on my boxen (stable, testing, testing + unstable).No such luck here.
If I run alien, I get the following error message:
# alien wxPythonGTK-py2.2-2.4.0.7-1.i386.rpm
Package build failed. Here's the log:
...
dh_installdirs
dpkg: unexpected output of `gcc --print-libgcc-file-name': `libgcc.a'
dpkg: compiler libgcc filename not understood: no gcc-lib part
dh_installdirs:
make: *** [binary-arch] Error 1
So it seems I'm stuck.
# alien wxPythonGTK-py2.2-2.4.0.7-1.i386.rpm
wxpythongtk-py2.2_2.4.0.7-2_i386.deb generated
Works for me on this Debian Woody system. It seems your gcc
installation is broken. gcc --print-libgcc-file-name should return a
full path specification, while yours seems to return only the filename
itself. Have you been experimenting with newer/alternative gcc
installations?
Regards,
Charl
On Wed, 2003-03-26 at 10:50, Antoon Pardon wrote:
On Sat, Mar 22, 2003 at 01:02:53AM +0100, Charl P. Botha wrote:
> On Fri, Mar 21, 2003 at 03:59:12PM -0800, Robin Dunn wrote:
--
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/
Well I have a Sarge system, and I installed gcc-3.2 because when
I tried to start from the source wxPython gcc-3.2 was one of the build-deps.
On Wed, Mar 26, 2003 at 11:09:58AM +0100, Charl P. Botha wrote:
On Wed, 2003-03-26 at 10:50, Antoon Pardon wrote:
> On Sat, Mar 22, 2003 at 01:02:53AM +0100, Charl P. Botha wrote:
> > I find the easiest way is to run alien on the your RPMs. The resultant deb
> > installs and runs fine on my boxen (stable, testing, testing + unstable).
>
> No such luck here.
>
> If I run alien, I get the following error message:
>
> # alien wxPythonGTK-py2.2-2.4.0.7-1.i386.rpm
> Package build failed. Here's the log:
...
> dh_installdirs
> dpkg: unexpected output of `gcc --print-libgcc-file-name': `libgcc.a'
> dpkg: compiler libgcc filename not understood: no gcc-lib part
> dh_installdirs:
> make: *** [binary-arch] Error 1
> So it seems I'm stuck.# alien wxPythonGTK-py2.2-2.4.0.7-1.i386.rpm
wxpythongtk-py2.2_2.4.0.7-2_i386.deb generatedWorks for me on this Debian Woody system. It seems your gcc
installation is broken. gcc --print-libgcc-file-name should return a
full path specification, while yours seems to return only the filename
itself. Have you been experimenting with newer/alternative gcc
installations?
--
Antoon Pardon
Well, now you know the reason why they call it "cutting" or "bleeding"
edge. 
Yes, I know sarge isn't unstable, but it's not stable either.
If you can get your gcc installation fixed (at least with regards to
--print-libgcc-file-name) the conversion will hopefully work.
On Wed, 2003-03-26 at 11:57, Antoon Pardon wrote:
On Wed, Mar 26, 2003 at 11:09:58AM +0100, Charl P. Botha wrote:
> On Wed, 2003-03-26 at 10:50, Antoon Pardon wrote:
> > On Sat, Mar 22, 2003 at 01:02:53AM +0100, Charl P. Botha wrote:> > > I find the easiest way is to run alien on the your RPMs. The resultant deb
> > > installs and runs fine on my boxen (stable, testing, testing + unstable).
> >
> > No such luck here.
> >
> > If I run alien, I get the following error message:
> >
> > # alien wxPythonGTK-py2.2-2.4.0.7-1.i386.rpm
> > Package build failed. Here's the log:
> ...
> > dh_installdirs
> > dpkg: unexpected output of `gcc --print-libgcc-file-name': `libgcc.a'
> > dpkg: compiler libgcc filename not understood: no gcc-lib part
> > dh_installdirs:
> > make: *** [binary-arch] Error 1
> > So it seems I'm stuck.
>
> # alien wxPythonGTK-py2.2-2.4.0.7-1.i386.rpm
> wxpythongtk-py2.2_2.4.0.7-2_i386.deb generated
>
> Works for me on this Debian Woody system. It seems your gcc
> installation is broken. gcc --print-libgcc-file-name should return a
> full path specification, while yours seems to return only the filename
> itself. Have you been experimenting with newer/alternative gcc
> installations?Well I have a Sarge system, and I installed gcc-3.2 because when
I tried to start from the source wxPython gcc-3.2 was one of the build-deps.
--
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/
Antoon Pardon wrote:
The offical package seems blocked at 2.4.0.3
Have you tried asking the package maintainer about a new version? He is usually fairly prompt about making them.
I thought about starting from the source package and if that worked,
getting the 2.4.0.7 and see if I could make my own, but getting the
build-deps, stated I had to install some specific packages, but
installing those would force me further in the direction of unstable
than I'm confortable with.So it seems I'm stuck.
Unless you want to build the old fashioned way without using a .deb... (I know, I know. I don't do that anymore either.)
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!