Hi,
every time I run configure I wonder if we really need g77. Should this check be removed?
checking for powerpc-linux-gnu-g77... powerpc-linux-gnu-g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether powerpc-linux-gnu-g77 accepts -g... yes checking the maximum length of command line arguments... 32768
BTW, a debian package of 0.42pre0 will be uploaded soon.
With best wishes,
Wolfi
On Thu, Jun 30, 2005 at 02:13:42PM +0200, Wolfram Quester wrote:
every time I run configure I wonder if we really need g77. Should this check be removed?
It seems to be triggered by
AM_PROG_LIBTOOL
AFAICT, the check for g77 isn't because of anything wrong in inkscape's configure.ac file.
BTW, a debian package of 0.42pre0 will be uploaded soon.
Great! It's good to get the wider testing of users of Debian unstable.
pjrm.
On Thu, Jun 30, 2005 at 11:10:05PM +1000, Peter Moulder wrote:
On Thu, Jun 30, 2005 at 02:13:42PM +0200, Wolfram Quester wrote:
every time I run configure I wonder if we really need g77. Should this check be removed?
It seems to be triggered by
AM_PROG_LIBTOOL
AFAICT, the check for g77 isn't because of anything wrong in inkscape's configure.ac file.
OK, thanks.
BTW, a debian package of 0.42pre0 will be uploaded soon.
Great! It's good to get the wider testing of users of Debian unstable.
Bad news here: there is a change of the C++ ABI going on in unstable, so uploads of programs using this ABI are blocked until the transition is over. Perhaps I start building packages for sarge, but I wanted to do this for the final release only.
With best wishes,
Wolfi
pjrm.
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
BTW, a debian package of 0.42pre0 will be uploaded soon.
Great! It's good to get the wider testing of users of Debian unstable.
Bad news here: there is a change of the C++ ABI going on in unstable, so uploads of programs using this ABI are blocked until the transition is over.
I haven't followed debian-devel discussion, but I'd be inclined to interpret
The ABI change will not start, before gcc-3.4.4, gcc-4.0.1 and binutils 2.16.1 are released and available on all architectures.
(from http://lists.debian.org/debian-devel-announce/2005/06/msg00004.html)
as meaning that the C++ freeze won't start until those package versions are in unstable. (They aren't in unstable when I checked just now.)
It's a bit more explicit further down:
- C++ program maintainers: ... Once packages with the new C++ ABI are uploaded, you must not upload your package until all C++ build dependencies are updated for the new ABI.
I'd guess that no "packages with the new C++ ABI" will be uploaded until those gcc/binutils package versions are in unstable.
That should allow us to get one or more iterations of 0.42pre packagings into unstable before the freeze.
While waiting, we can look for g++-4-related bug reports on our build dependencies, and work on having those fixed so that our dependencies can be in unstable as soon as possible so that future inkscape uploads can be in unstable as soon as possible after the freeze starts. Perhaps post a list of all such bug numbers in this thread.
pjrm.
My own experience with gtkmm and gcc 4.0 is there are still some problem spots unless everything is re-compiled in 4.0. So, the transition will probably be a bit messy for the next couple of months. Thus, my advice is to try to release 0.42 under 3.3.5, and plan for the next release under 4.0 when most of the supporting library packages should be under 4.0. John
Peter Moulder wrote:
BTW, a debian package of 0.42pre0 will be uploaded soon.
Great! It's good to get the wider testing of users of Debian unstable.
Bad news here: there is a change of the C++ ABI going on in unstable, so uploads of programs using this ABI are blocked until the transition is over.
I haven't followed debian-devel discussion, but I'd be inclined to interpret
The ABI change will not start, before gcc-3.4.4, gcc-4.0.1 and binutils 2.16.1 are released and available on all architectures.
(from http://lists.debian.org/debian-devel-announce/2005/06/msg00004.html)
as meaning that the C++ freeze won't start until those package versions are in unstable. (They aren't in unstable when I checked just now.)
It's a bit more explicit further down:
- C++ program maintainers: ... Once packages with the new C++ ABI are uploaded, you must not upload your package until all C++ build dependencies are updated for the new ABI.
I'd guess that no "packages with the new C++ ABI" will be uploaded until those gcc/binutils package versions are in unstable.
That should allow us to get one or more iterations of 0.42pre packagings into unstable before the freeze.
While waiting, we can look for g++-4-related bug reports on our build dependencies, and work on having those fixed so that our dependencies can be in unstable as soon as possible so that future inkscape uploads can be in unstable as soon as possible after the freeze starts. Perhaps post a list of all such bug numbers in this thread.
pjrm.
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi,
On Mon, Jul 04, 2005 at 07:29:09AM -0600, John Taber wrote:
My own experience with gtkmm and gcc 4.0 is there are still some problem spots unless everything is re-compiled in 4.0. So, the transition will probably be a bit messy for the next couple of months. Thus, my advice is to try to release 0.42 under 3.3.5, and plan for the next release under 4.0 when most of the supporting library packages should be under 4.0. John
I don't think that this would be a good way to go. You could Build-Depend on gcc-3.3.5, yes, but step by step the libraries we depend on will be recompiled with gcc-4.0, which will lead to to a mess. Please correct me if I got you wrong.
BTW, I think I'll create backports for sarge (ppc and i386 at least) once 0.42 is released. These packages can be uploaded to sf's download page together with dsc and diff.gz.
Thanks,
Wolfi
On Mon, Jul 04, 2005 at 09:10:19PM +1000, Peter Moulder wrote:
The ABI change will not start, before gcc-3.4.4, gcc-4.0.1 and binutils 2.16.1 are released and available on all architectures.
(from http://lists.debian.org/debian-devel-announce/2005/06/msg00004.html)
as meaning that the C++ freeze won't start until those package versions are in unstable.
This has now changed:
http://lists.debian.org/debian-devel-announce/2005/07/msg00001.html
and indeed the C++ transition has now begun.
libsigc++ has already been uploaded using g++ 4.0's ABI (late Jul 5); we are now waiting for libglibmm to be uploaded, and then libgtkmm can be uploaded, and then inkscape can be uploaded.
No g++-4-related bugs are filed against any of these packages.
The bug database suggests that Debian's libglibmm maintainer isn't very active, but OTOH any Debian developer is allowed to upload updated versions of another person's package 5 days after that package's dependencies become available in 4.0 form. Thus, with luck, inkscape could be uploadable in as little as a week's time -- or easily within July, anyway.
pjrm.
Hi alltogether,
I'll have only sporadic internet access during the next two to three weeks and I therefore cannot grant that I can arrange an upload of inkscape 0.42 in time. I prepared packages of 0.42pre1 compiled for sarge on i386 and ppc, two architectures I have easy access to. They can be downloaded from http://honk.physik.uni-konstanz.de/~wolfi/inkscape/ Files snd md5sums are 1e23fed2605f9ca399ae879d6c8db7b6 inkscape_0.41+0.42pre1.orig.tar.gz b96abd76d8f20e7fc4ec8c9774c94b8d inkscape_0.41+0.42pre1-sarge1.diff.gz 70a7e9752e3b6c09f89225cf57f88920 inkscape_0.41+0.42pre1-sarge1.dsc 65a3d61a5c75f9bea2116faea3b66ef8 inkscape_0.41+0.42pre1-sarge1_i386.deb 8c6b984b7801439de68c7484144e44e6 inkscape_0.41+0.42pre1-sarge1_powerpc.deb
inkscape_0.41+0.42pre1.orig.tar.gz is just our tarball renamed to fit into debian's build process,dsc and diff.gz are provided so that other debian users can build their own packages. Perhaps the two debs can be added to sf's download area. When 0.42 is released I plan to provide sarge-backports on this site for at least these two architectures.
Thanks,
Wolfi
participants (3)
-
John Taber -
Peter Moulder -
Wolfram Quester