Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot 2012.11 large file support
Date: Wed, 12 Dec 2012 11:16:28 +0100	[thread overview]
Message-ID: <20121212111628.5d1e9dba@skate> (raw)
In-Reply-To: <50C7D14F.4060304@mind.be>

Dear Arnout Vandecappelle,

On Wed, 12 Dec 2012 01:35:27 +0100, Arnout Vandecappelle wrote:

>   Except for the environment, I don't expect we'll see much interesting
> in these...
> 
>   Probably more useful are all the config.log under output/toolchain/gcc*
> (especially output/toolchain/gcc-*-final/*/libgcc/config.log and config.h)

I have now reproduced the problem on a fresh installation of Ubuntu
12.04 32 bits. Nothing fancy in my system: it is an Ubuntu server, with
just the base packages + the minimal dependencies for Buildroot to run.

I have posted at
http://free-electrons.com/~thomas/pub/largefile-build-problem.tar.gz a
tarball that contains:

logfile <-- this is the full build log
output/build/host-autoconf-2.68/config.log
output/build/host-gmp-5.0.5/config.log
output/build/host-mpc-1.0.1/config.log
output/build/host-m4-1.4.16/config.log
output/build/host-mpfr-3.1.1/config.log
output/build/host-libtool-2.2.10/config.log
output/build/host-binutils-2.21.1/libiberty/config.log
output/build/host-binutils-2.21.1/binutils/config.log
output/build/host-binutils-2.21.1/bfd/config.log
output/build/host-binutils-2.21.1/config.log
output/build/host-binutils-2.21.1/gprof/config.log
output/build/host-binutils-2.21.1/intl/config.log
output/build/host-binutils-2.21.1/gas/config.log
output/build/host-binutils-2.21.1/etc/config.log
output/build/host-binutils-2.21.1/ld/config.log
output/build/host-binutils-2.21.1/opcodes/config.log
output/build/host-automake-1.11.6/config.log
output/toolchain/gcc-4.6.3-initial/libiberty/config.log
output/toolchain/gcc-4.6.3-initial/libdecnumber/config.log
output/toolchain/gcc-4.6.3-initial/lto-plugin/config.log
output/toolchain/gcc-4.6.3-initial/libcpp/config.log
output/toolchain/gcc-4.6.3-initial/zlib/config.log
output/toolchain/gcc-4.6.3-initial/config.log
output/toolchain/gcc-4.6.3-initial/build-i686-pc-linux-gnu/libiberty/config.log
output/toolchain/gcc-4.6.3-initial/build-i686-pc-linux-gnu/fixincludes/config.log
output/toolchain/gcc-4.6.3-initial/fixincludes/config.log
output/toolchain/gcc-4.6.3-initial/intl/config.log
output/toolchain/gcc-4.6.3-initial/gcc/config.log
output/toolchain/gcc-4.6.3-intermediate/libiberty/config.log
output/toolchain/gcc-4.6.3-intermediate/libdecnumber/config.log
output/toolchain/gcc-4.6.3-intermediate/lto-plugin/config.log
output/toolchain/gcc-4.6.3-intermediate/libcpp/config.log
output/toolchain/gcc-4.6.3-intermediate/zlib/config.log
output/toolchain/gcc-4.6.3-intermediate/config.log
output/toolchain/gcc-4.6.3-intermediate/build-i686-pc-linux-gnu/libiberty/config.log
output/toolchain/gcc-4.6.3-intermediate/build-i686-pc-linux-gnu/fixincludes/config.log
output/toolchain/gcc-4.6.3-intermediate/fixincludes/config.log
output/toolchain/gcc-4.6.3-intermediate/i586-buildroot-linux-uclibc/libgcc/config.log
output/toolchain/gcc-4.6.3-intermediate/intl/config.log
output/toolchain/gcc-4.6.3-intermediate/gcc/config.log
output/toolchain/uClibc-0.9.33.2/.config

I haven't looked into them for now.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

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

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 12:35 [Buildroot] buildroot 2012.11 large file support Berns
2012-12-10 14:53 ` Willy Lambert
2012-12-10 19:20   ` Peter Korsgaard
2012-12-10 19:38     ` Willy Lambert
2012-12-10 20:38       ` Peter Korsgaard
2012-12-10 21:30         ` Willy Lambert
2012-12-10 22:05           ` Peter Korsgaard
2012-12-11  2:13             ` Willy Lambert
2012-12-11  7:04               ` Peter Korsgaard
2012-12-11  8:43                 ` Willy Lambert
2012-12-11  9:09                   ` Thomas Petazzoni
2012-12-12  1:04                     ` Willy Lambert
2012-12-11 15:09           ` Willy Lambert
2012-12-11 16:10             ` Thomas Petazzoni
2012-12-12  0:35               ` Arnout Vandecappelle
2012-12-12 10:16                 ` Thomas Petazzoni [this message]
2012-12-12 11:01                   ` Thomas Petazzoni
2012-12-12 11:03                     ` Thomas Petazzoni
2012-12-12 12:47                       ` Thomas Petazzoni
2012-12-12 16:47                         ` Peter Korsgaard
2012-12-12 17:32                           ` Thomas Petazzoni
2012-12-12 20:15                             ` Peter Korsgaard
2012-12-12 22:21                               ` Thomas Petazzoni
2012-12-12 23:47                                 ` Arnout Vandecappelle
2012-12-13 10:45                                   ` Victor Hiairrassary
2012-12-13 10:55                                     ` Peter Korsgaard
2012-12-13 11:06                                     ` Arnout Vandecappelle
2012-12-13 11:28                                       ` Victor Hiairrassary
2012-12-12  9:20               ` Willy Lambert
2012-12-12 10:21     ` Fabio Porcedda
2012-12-11  9:30 ` Berns
2012-12-12  6:05   ` Peter Korsgaard

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=20121212111628.5d1e9dba@skate \
    --to=thomas.petazzoni@free-electrons.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