I noticed that problem too, but it seems it happens only when building
packages with dpkg-buildpacakge. I tried with debuild and pdebuild, and
both ways produce packages with modules in the right directory,
linux-gnu-i486, for e_modules and engage
Didn't understand why, though :/
Regards
Lut!n
On Sun, Jul 16, 2006 at 08:02:39PM +0200, N-Mi wrote:
> Hello,
>
> I'd like to make a suggestion on how debian packages for e_modules
> should be built.
>
> At present, the problem is that all modules are built at once, and
> package generation for all modules fails when ONE module fails to bui
On Sun, 16 Jul 2006 21:07:45 +0200 N-Mi <[EMAIL PROTECTED]> wrote:
> David Seikel a écrit :
> >
> > Autotools and compiling can both benefit from their own caching
> > mechanisms.
>
> I was about to make another post (as it doesn't apply only to
> e_modules) to make a suggestion on autotools ca
David Seikel a écrit :
>
> Autotools and compiling can both benefit from their own caching
> mechanisms. The autotools configurations are usually copied around and
> tweaked rather than being written from scratch, mostly coz not many
> people understand autotools. It shows, many of them are chec
On Sun, 16 Jul 2006 20:02:39 +0200 N-Mi <[EMAIL PROTECTED]> wrote:
> At present, the problem is that all modules are built at once, and
> package generation for all modules fails when ONE module fails to
> build. Additionaly, autoconf/automake process is very long (I think
> it's most of the time
