Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Beaglebone build broken ?
Date: Fri, 7 Sep 2012 17:40:01 +0530	[thread overview]
Message-ID: <5049E419.2050408@synopsys.com> (raw)

Hi,

I'm using the tip of buildroot, to build for beaglebone (using
beaglebone_defconfig) and running into a couple of issues:

1. The hard FPU settings cause uClibc build to break (intermixing of
soft and hard) and an equivalent of below needs to be made to top level
config file.

-BR2_EXTRA_GCC_CONFIG_OPTIONS="--with-fpu=vfpv3 --with-float=hard"
+BR2_EXTRA_GCC_CONFIG_OPTIONS="--with-float=soft"
-# BR2_SOFT_FLOAT is not set
+BR2_SOFT_FLOAT=y

If this is a must, can this be committed to buildroot itself. I can't
propose a patch myself because I'm not sure why it must or must-not be
built with software float.

2. Next, it's failing when trying to get the custom kernel.

Cloning into bare repository
linux-linux-ti33x-psp-3.2-r5a+gitr09e9651bcf2ee8d86685f2a8075bc6557b1d3b91...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
--2012-09-07 12:54:37-- 
http://sources.buildroot.net//linux-linux-ti33x-psp-3.2-r5a+gitr09e9651bcf2ee8d86685f2a8075bc6557b1d3b91.tar.gz
Resolving sources.buildroot.net... 176.9.16.109
Connecting to sources.buildroot.net|176.9.16.109|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-09-07 12:54:38 ERROR 404: Not Found.

A few months back I could successfully build bone image so obviously
this kernel issue was not present then.


Thanks,
Vineet

             reply	other threads:[~2012-09-07 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 12:10 Vineet Gupta [this message]
2012-09-07 12:49 ` [Buildroot] Beaglebone build broken ? Frank Hunleth
2012-09-10 16:35   ` Alexandre Belloni
2012-09-11  4:19     ` Vineet Gupta
2012-09-11 23:18       ` Alexandre Belloni

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=5049E419.2050408@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=buildroot@busybox.net \
    /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