Eduard Bloch a écrit :

#include <hallo.h>
* Filipus Klutiero [Fri, Jan 20 2006, 03:56:56AM]:

As said, there is no point in making a module-source package depend on
certain compiler version because they are independent.

OK, but many module-source packages still do that. If you agree that depending on the gcc meta package is equivalent to depending on a specific gcc version, I'll consider filing bugs against module-source packages which depend on gcc.

The kernel
defines that dependency and it can only be resolved while preparing the
actual build. It is not even done by "m-a prepare", but I will change
that a bit and install the compiler needed for the current kernel (or
the alternative build-tree(s) specified with -k/-l options).
That's great, I guess we understood now. Sorry if the original report was unclear.

That you filled your report against the wrong package. Luckily I am the
author of m-a as well and yes, you are right, it should be fixed
up-front in m-a.

OK, as I said I wasn't sure if this should have been filed directly against m-a.

Hmm, an interactive solution. Sounds feasible... a verbose failure in
non-interactive mode and a such prompt in cli/dialog modes.
Yep :)

That would be another prompt: 'Build essential packages are missing,
your system is not ready to compile modules. Do you wish the automatic
environment preparation to be started now?'

Please correct that if you are a native speaker or suggest a better
phrase.

Does your message mean that m-a will install build-essential, or just the packages essential for building the specific module? If you mean m-a will install b-e, this looks a little overkill compared to installing the needed gcc, but it might be the most optimal solution (I can see for example that I don't need g++ or libc6-dev to build rt2500). If you mean instead that m-a will try to pick just the really needed packages, referring to "Build essential packages" looks a bit idiomatic, but I'm not a native speaker. Perhaps "Some packages essential to compile the module(s) are missing. Do you want those packages to be installed now, or should the compilation of the module(s) be attempted anyway (this will most likely fail)?"

Filipus

Reply via email to