mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: building sandbox barebox: too many '"BITS_PER_LONG" redefined' warnings
Date: Tue, 2 Jun 2015 11:37:36 +0300	[thread overview]
Message-ID: <20150602113736.07b93fb60300ecf8754272a7@gmail.com> (raw)

Hi, Sascha!

I have tried to build sandbox barebox from latest next on amd64 debian linux host.

I see very many '"BITS_PER_LONG" redefined' warnings, e.g.

  CC      common/misc.o
In file included from /home/antony/barebog.git/arch/sandbox/include/asm/types.h:57:0,
                 from include/linux/types.h:5,
                 from include/param.h:5,
                 from include/console.h:23,
                 from include/stdio.h:5,
                 from include/common.h:23,
                 from common/misc.c:19:
include/asm-generic/bitsperlong.h:7:0: warning: "BITS_PER_LONG" redefined
 #define BITS_PER_LONG 32
 ^
In file included from include/asm-generic/posix_types.h:4:0,
                 from /home/antony/barebog.git/arch/sandbox/include/asm/posix_types.h:1,
                 from include/linux/posix_types.h:46,
                 from include/linux/types.h:4,
                 from include/param.h:5,
                 from include/console.h:23,
                 from include/stdio.h:5,
                 from include/common.h:23,
                 from common/misc.c:19:
/home/antony/barebog.git/arch/sandbox/include/asm/bitsperlong.h:5:0: note: this is the location of the previous definition
 #define BITS_PER_LONG 64
 ^

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2015-06-02  8:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02  8:37 Antony Pavlov [this message]
2015-06-03  7:55 ` Sascha Hauer

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=20150602113736.07b93fb60300ecf8754272a7@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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