On 9 October 2006 at 18:16, Dirk Eddelbuettel wrote:
> On 9 October 2006 at 17:05, Stefan Heim wrote:
> | Package: octave2.0-headers
> | Version: 2.0.17-9
> | Severity: important
> |
> | The /usr/bin/mkoctfile command in this package explicitly refers
> | {gcc,g77,g++}-2.95 but the package's control file is missing a Depends:
> | for these compilers. As a result, mkoctfile does annoyingly not work
> | inside a pbuilder chroot jail for sarge without manual intervention.
> |
> | I strongly suggest adding gcc-2.95, g++-2.95 and g77-2.95 to the Depends:
> | line in debian/control to fix the problem.
>
> This is only present in stable and oldstable:
>
> [EMAIL PROTECTED]:~$ rmadison octave2.0-headers
> octave2.0-headers | 2.0.16.92-7 | oldstable | all
> octave2.0-headers | 2.0.17-9 | stable | all
> [EMAIL PROTECTED]:~$
>
> As the term 'stable' aims to say, the software packages in the 'stable',
> and by extension of course also in the previous release 'oldstable')
> releases are not altered (unless, say, a security fix is needed).
That's clear. I didn't realize that there's no octave2.0* in sid/etch anymore.
Sorry for the noise.
> It's been a while, but I'd also think that the -2.95 toolchain was the
> default then, so a Depends: was not needed as it was implicit.
At least since 7 Jan 2003 (build-essential-9.1), build-essential depends on
gcc >= 3.2 ...
> Can you
> not get a 'build-essential' equivalent into the stable pbuilder chroot ?
Of course I have build-essential inside the chroot. But inside the chroot:
[EMAIL PROTECTED]:/# apt-cache show build-essential | grep ^Depends
Depends: libc6-dev | libc-dev, gcc (>= 3:3.3), g++ (>= 3:3.3), make, dpkg-dev
(>= 1.4.1.19)
So nothing from -2.95 tooclchain gets drawn in. But I can explicitly add
g++-2.95 to the Depends: of the package that fails to build in the sarge
chroot. Ugly, but works.
> Current octave-*-headers packages appear to work.
Yes, they have the compiler dependencies stated.
-Stefan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
