On Mon, May 13, 2013 at 11:52:09AM +0930, Rusty Russell wrote:
> Guenter Roeck writes:
> > Attached is a failing configuration for x86_64. Note that
> > drivers/staging/android/logger.c fails to build with this configuration,
> > so you have to build it with make -i to see the problem.
> >
> > Loo
Guenter Roeck writes:
> Attached is a failing configuration for x86_64. Note that
> drivers/staging/android/logger.c fails to build with this configuration,
> so you have to build it with make -i to see the problem.
>
> Looking through my logs, it seems that the problem may be related to other
> b
Hi Rusty,
On Thu, May 09, 2013 at 10:26:00AM +0930, Rusty Russell wrote:
> Guenter Roeck writes:
> > Hi all,
> >
> > I started seeing build failures such as the following in the last week or
> > so.
> >
> > make[2]: [__modpost] Error 1
> >
> > followed by lots of messages such as
> >
> > gcc: er
Guenter Roeck writes:
> Hi all,
>
> I started seeing build failures such as the following in the last week or so.
>
> make[2]: [__modpost] Error 1
>
> followed by lots of messages such as
>
> gcc: error: arch/x86/crypto/ablk_helper.mod.c: No such file or directory
> gcc: fatal error: no input file
Hi all,
I started seeing build failures such as the following in the last week or so.
make[2]: [__modpost] Error 1
followed by lots of messages such as
gcc: error: arch/x86/crypto/ablk_helper.mod.c: No such file or directory
gcc: fatal error: no input files
(at least if I run make -i)
After r
5 matches
Mail list logo
