Alpha arch development list
 help / color / mirror / Atom feed
From: Simon Brown <lists@700c.org>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: linux-alpha@vger.kernel.org
Subject: Re: [BUG] net/core/sock.c won't compile on alpha
Date: Wed, 22 Aug 2012 22:20:24 +0100	[thread overview]
Message-ID: <87haruei93.wl%lists@700c.org> (raw)
In-Reply-To: <20120822121407.GA6257@gherkin.frus.com>

Bob,

Is this a different issue to the one discussed and fixed earlier in the month
with this email subject:
Re: [next:akpm 129/309] net/core/sock.c:274:36: error: initializer element is not constant

Sounds very similar.

Simon

At Wed, 22 Aug 2012 07:14:07 -0500,
Bob Tracy wrote:
> 
> Kernel version 3.6.0-rc2, and probably -rc1 as well.  I get the
> following compile-time error on alpha architecture:
> 
> (...)
>   CC      net/core/sock.o
> net/core/sock.c:274:36: error: initializer element is not constant
> net/core/sock.c:274:36: error: (near initialization for "memalloc_socks")
> net/core/sock.c:274:36: error: initializer element is not constant
> make[2]: *** [net/core/sock.o] Error 1
> make[1]: *** [net/core] Error 2
> make: *** [net] Error 2
> 
> Compiler is gcc-4.6.3.
> 
> Line 274 of net/core/sock.c is
> 
> struct static_key memalloc_socks = STATIC_KEY_INIT_FALSE;
> 
> which made its first appearance in 3.6.0-rc1.
> 
> --Bob
> --
> To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      parent reply	other threads:[~2012-08-22 21:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 12:14 [BUG] net/core/sock.c won't compile on alpha Bob Tracy
2012-08-22 21:16 ` Michael Cree
2012-08-23  5:20   ` Bob Tracy
2012-08-22 21:20 ` Simon Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87haruei93.wl%lists@700c.org \
    --to=lists@700c.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=rct@gherkin.frus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox