mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Vikram Narayanan <vikram186@gmail.com>
To: "Murthy, Ramana" <Ramana.Murthy@microsemi.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: sandbox build failing on redhat host
Date: Sat, 16 Jul 2011 12:15:52 +0530	[thread overview]
Message-ID: <CAHwEkO0EQFn+zBfKnry7R+H7g4tTiGzFLejz+n=Poj4KO47pZQ@mail.gmail.com> (raw)
In-Reply-To: <6F2524F76379064FB8CB9CEE698D56DA8D40E67E80@IN-MSG-01.amer.actel.com>

On Wed, Jun 8, 2011 at 9:46 AM, Murthy, Ramana
<Ramana.Murthy@microsemi.com> wrote:
> Hi All,
>
>
>
> Can somebody please help me on this. I know sandbox is not priority. But
> this helps me to progress to create a new port.

Please post your .config file.
Which version of barebox you are using?

-
Vikram
>
> Best Regards,
>
> N.S.S.R.Murthy,
>
> Ph # +91-40-67303600, Extn – 3731,
>
> Mobile # +91-9959677780.
>
>
>
> From: Murthy, Ramana
> Sent: Monday, June 06, 2011 3:48 PM
> To: 'barebox@lists.infradead.org'
> Subject: sandbox build failing on redhat host
>
>
>
> Hi All,
>
>
>
> I am trying to build barebox with ARCH = sandbox. My make menuconfig is
> successful.
>
> But the actual build is throwing below errors. As I understand, the errors
> are because offt_build.c that includes <asm/barebox.h>. But in case of
> ARCH=sandbox,the arch/sandbox/inlcude/asm/barebox.h contains nothing. Is
> itsupposed to compile ft_build.c in case of sandbox?
>
>  CHK     include/generated/version.h
>  CHK     include/generated/utsrelease.h
>  SYMLINK include/config.h -> arch/sandbox/board//config.h
>  CC      scripts/mod/empty.o
>  HOSTCC  scripts/mod/mk_elfconfig
>  MKELF   scripts/mod/elfconfig.h
>  HOSTCC  scripts/mod/modpost.o
>  HOSTCC  scripts/mod/sumversion.o
>  HOSTLD  scripts/mod/modpost
>  HOSTCC  scripts/bin2c
>  HOSTCC  scripts/mkimage
>  HOSTCC  scripts/bareboxenv
>  CC      common/hush.o
>  CC      common/date.o
>  CC      common/ft_build.o
> In file included from common/ft_build.c:33:
> include/ft_build.h:59: error: syntax error before "bd_t"
> include/ft_build.h:59: warning: function declaration isn't a prototype
> include/ft_build.h:65: error: syntax error before "bd_t"
> include/ft_build.h:65: warning: function declaration isn't a prototype
> include/ft_build.h:66: error: syntax error before "bd_t"
> include/ft_build.h:66: warning: function declaration isn't a prototype
> include/ft_build.h:67: error: syntax error before "bd_t"
> include/ft_build.h:67: warning: function declaration isn't a prototype
> common/ft_build.c:458: error: syntax error before "bd_t"
> common/ft_build.c:459: warning: function declaration isn't a prototype
> common/ft_build.c: In function `ft_setup':
> common/ft_build.c:477: error: `blob' undeclared (first use in this function)
> common/ft_build.c:477: error: (Each undeclared identifier is reported only
> once
> common/ft_build.c:477: error: for each function it appears in.)
> common/ft_build.c:477: error: `bd' undeclared (first use in this function)
> common/ft_build.c:488: error: `initrd_start' undeclared (first use in
> this function)
> common/ft_build.c:488: error: `initrd_end' undeclared (first use in
> this function)
> common/ft_build.c:460: warning: unused variable `p'
> common/ft_build.c:461: warning: unused variable `len'
> common/ft_build.c:463: warning: unused variable `clock'
> make[1]: *** [common/ft_build.o] Error 1
> make: *** [common] Error 2
>
>
>
> Best Regards,
>
> N.S.S.R.Murthy,
>
> Ph # +91-40-67303600, Extn – 3731,
>
> Mobile # +91-9959677780.
>
>
>
> ________________________________
> The information contained in or attached to this email may be subject to the
> Export Administration Regulations (EAR), administered by the U.S. Department
> of Commerce, or the International Traffic in Arms Regulations (ITAR),
> administered by the U.S. Department of State, and may require an export
> license from the Commerce or State Department prior to its export. An export
> can include a release or disclosure to a foreign national inside or outside
> the United States. Include this notice with any reproduced portion of this
> information.
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
>

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

  reply	other threads:[~2011-07-16  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AcwkMvQr2IoEFQV9To6jK9T6RQPvyABX9l1w>
2011-06-08  4:16 ` Murthy, Ramana
2011-07-16  6:45   ` Vikram Narayanan [this message]
2011-07-19  5:30     ` Murthy, Ramana
2011-07-19 10:22       ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-19 10:53         ` Murthy, Ramana
2011-07-20  4:39           ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-06 10:17 Murthy, Ramana
2011-06-10  7:22 ` 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='CAHwEkO0EQFn+zBfKnry7R+H7g4tTiGzFLejz+n=Poj4KO47pZQ@mail.gmail.com' \
    --to=vikram186@gmail.com \
    --cc=Ramana.Murthy@microsemi.com \
    --cc=barebox@lists.infradead.org \
    /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