Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#269867: acknowledged by developer (Bug#269867: fixed in toolchain-source 3.4-3)

3 views
Skip to first unread message

Martin-Éric Racine

unread,
Dec 31, 2004, 11:10:14 AM12/31/04
to
On Thu, 30 Dec 2004, Debian Bug Tracking System wrote:

> We believe that the bug you reported is fixed in the latest version of
> toolchain-source, which is due to be installed in the Debian FTP archive:

[...]
> toolchain-source (3.4-3) unstable; urgency=low
> * gcc package now generated from the native gcc source package
> (closes: #267449, #267473, #253608, #269867)


Thanks for these fixes introduced in the 3.4-3 package. Unfortunately, I have
to reopen this bug, because the following parts are still not fixed:

> > 1) use version (>= ${Source-Version}) for Depends or Recommends on gcc,
> > gcc-doc, etc.

binutils-<target>-linux still depends on:
gcc (>= 2.95.2-1)
binutils (>= 2.9.5.0.12)
debhelper (>= 3)

Should probably be:
gcc (>= ${Source-Version})
binutils (>= 2.15)
debhelper (>= 4.2)


> > 2) use a more recent Debian standard version that won't make Lintian
> > complain. :)

binutils-<target>-linux control file is still at standard version 3.0.1.1.


> > 3) mention Provides cpp, gcc, g++ equal to (>= ${Source-Version}) for
> > gcc-<target>-linux package.

Done. Thanks.


> > 4) mention Provides cross libstd++6 and cross libstd++-dev for
> > gcc-<target>-linux package.

Fixed by generating separate packages. Thanks.


*****

Along the same type of bugs, I notice that binutils is generated with the user
as Maintainer, while gcc is generated with Debian GCC Maintainers as maintainer.

IMHO, it should probably be the user in both cases, since the Debian GCC team
cannot be held responsible of a user's sel-built cross-compiler.


--
Martin-Éric Racine, ICT Consultant
http://www.iki.fi/q-funk/

Hakan Ardo

unread,
Jan 2, 2005, 7:00:12 AM1/2/05
to
On Fri, Dec 31, 2004 at 04:46:35PM +0200, Martin-Éric Racine wrote:
>
> > > 1) use version (>= ${Source-Version}) for Depends or Recommends on gcc,
> > > gcc-doc, etc.
>
> binutils-<target>-linux still depends on:
> gcc (>= 2.95.2-1)
> binutils (>= 2.9.5.0.12)
> debhelper (>= 3)
>
> Should probably be:
> gcc (>= ${Source-Version})

Won't ${Source-Version} refere to the binutils version and not the
corresponding gcc version?

> binutils (>= 2.15)
> debhelper (>= 4.2)

You'r probably right here.

>
>
> > > 2) use a more recent Debian standard version that won't make Lintian
> > > complain. :)
>
> binutils-<target>-linux control file is still at standard version 3.0.1.1.

Right!

> Along the same type of bugs, I notice that binutils is generated with the user
> as Maintainer, while gcc is generated with Debian GCC Maintainers as maintainer.
>
> IMHO, it should probably be the user in both cases, since the Debian GCC team
> cannot be held responsible of a user's sel-built cross-compiler.

They should both have the user as Maintainer yes (I must have intreduced
some bug just before I released :(

--
Hakan Ardo


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Hakan Ardo

unread,
Jan 2, 2005, 8:00:15 AM1/2/05
to
On Fri, Dec 31, 2004 at 04:46:35PM +0200, Martin-Éric Racine wrote:
>
> > > 1) use version (>= ${Source-Version}) for Depends or Recommends on gcc,
> > > gcc-doc, etc.
>
> binutils-<target>-linux still depends on:
> gcc (>= 2.95.2-1)
> binutils (>= 2.9.5.0.12)
> debhelper (>= 3)
>
> Should probably be:
> gcc (>= ${Source-Version})
> binutils (>= 2.15)
> debhelper (>= 4.2)

You are talking about the Build-Depends here? Eg what compilers are needed
to build the binutils package, and I do think the stated requerments is
enough. So unless you've had problems build the binutils package with the
stated requrements I'll change the requrement on gcc to >= 3.3, and leve the
rest as they are.

Martin-Éric Racine

unread,
Jan 2, 2005, 1:40:11 PM1/2/05
to
On Sun, 2 Jan 2005, Hakan Ardo wrote:

> On Fri, Dec 31, 2004 at 04:46:35PM +0200, Martin-Éric Racine wrote:
> >
> > > > 1) use version (>= ${Source-Version}) for Depends or Recommends on gcc,
> > > > gcc-doc, etc.
> >
> > binutils-<target>-linux still depends on:
> > gcc (>= 2.95.2-1)
> > binutils (>= 2.9.5.0.12)
> > debhelper (>= 3)
> >
> > Should probably be:
> > gcc (>= ${Source-Version})
>
> Won't ${Source-Version} refere to the binutils version and not the
> corresponding gcc version?

Hmm... Right. how about using ${Depends:misc} to insert the value based on the
version of the toolchain-source package, via debian/rules?

> > Along the same type of bugs, I notice that binutils is generated with the user
> > as Maintainer, while gcc is generated with Debian GCC Maintainers as maintainer.
> >
> > IMHO, it should probably be the user in both cases, since the Debian GCC team
> > cannot be held responsible of a user's sel-built cross-compiler.
>
> They should both have the user as Maintainer yes (I must have intreduced
> some bug just before I released :(

Btw, is it normal for the resulting cross-GCC to depend upon cross-libgcc2 and
recursively on cross-libc6?

Martin-Éric Racine

unread,
Jan 2, 2005, 2:00:14 PM1/2/05
to
On Sun, 2 Jan 2005, Hakan Ardo wrote:

> On Fri, Dec 31, 2004 at 04:46:35PM +0200, Martin-Éric Racine wrote:
> >
> > > > 1) use version (>= ${Source-Version}) for Depends or Recommends on gcc,
> > > > gcc-doc, etc.
> >
> > binutils-<target>-linux still depends on:
> > gcc (>= 2.95.2-1)
> > binutils (>= 2.9.5.0.12)
> > debhelper (>= 3)
> >
> > Should probably be:
> > gcc (>= ${Source-Version})
> > binutils (>= 2.15)
> > debhelper (>= 4.2)
>
> You are talking about the Build-Depends here? Eg what compilers are needed
> to build the binutils package, and I do think the stated requerments is
> enough. So unless you've had problems build the binutils package with the
> stated requrements I'll change the requrement on gcc to >= 3.3, and leve the
> rest as they are.

Indeed build-depends. GCC >= 3.3 should be OK, although IIRC there was a change
of binary format on some arches since 3.4, so since toolchain-source is up to
3.4.3, maybe the same version should be build-depends for the host compiler.

Same thing for binutils.

For debhelper, I would at least put >= 4, just to be safe.

Hakan Ardo

unread,
Jan 3, 2005, 4:50:11 AM1/3/05
to
On Sun, Jan 02, 2005 at 08:32:35PM +0200, Martin-Éric Racine wrote:
> >
> > You are talking about the Build-Depends here? Eg what compilers are needed
> > to build the binutils package, and I do think the stated requerments is
> > enough. So unless you've had problems build the binutils package with the
> > stated requrements I'll change the requrement on gcc to >= 3.3, and leve the
> > rest as they are.
>
> Indeed build-depends. GCC >= 3.3 should be OK, although IIRC there was a change
> of binary format on some arches since 3.4, so since toolchain-source is up to
> 3.4.3, maybe the same version should be build-depends for the host compiler.

As 3.3 is the default compiler for debian system I wont demand anything more
unsless it is striclty necessery, and as far as I can tell 3.3 does a good job
in producing the compiler.

>
> Same thing for binutils.
>
> For debhelper, I would at least put >= 4, just to be safe.

OK

0 new messages