All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building latest arm
Date: Wed, 27 Jun 2007 18:20:03 +0200	[thread overview]
Message-ID: <20070627162003.GA8454@aon.at> (raw)
In-Reply-To: <6B9D9C36F5A26347A593D6945C470AE90F4031@delta-two.prga.net>

On Wed, Jun 27, 2007 at 07:45:02AM -0500, michael.miller at prga.com wrote:
>>-----Original Message-----
>>From: Bernhard Fischer [mailto:rep.dot.nop at gmail.com] 
>>Sent: Tuesday, June 26, 2007 1:22 AM
>>To: Michael D. Miller
>>Cc: buildroot at uclibc.org
>>Subject: Re: [Buildroot] Problem building latest arm
>>
>>On Mon, Jun 25, 2007 at 10:04:44PM -0500, michael.miller at prga.com
>wrote:
>>>I'm trying to build for an Xscale (ARM), EABI, NPTL with binutils 
>>>2.17.50.0.16, software floating point, and target options bash, bzip2 
>>>and diffutils.  All other options are default (gcc 4.2.0).  I'm using 
>>>the latest snapshot for uclibc, and have tried buildroot snapshots
>from 
>>>6/20, 6/21 and 6/23.
>>>
>>>If I use 6/20, 6/21 or 6/23 buildroot snapshots then the build fails
>in 
>>>pthreads because sysdep-cancel.h is not found.  Looking in the 
>>>linuxthreads/sysdeps/unix/sysv/linux directory, I see subdirectories 
>>>for i386, mips, etc. but not for arm.
>>>
>>>Searching recent mailing list archives, Bernhard says things that make
>
>>>me think this configuration should work.  He hints that helptext will
>>
>>I was talking about eabi. Threading is a different issue (but even that
>one has a nice, >IMHO descriptive help-text).
>
>I tried just building for "old" Linux threads instead of POSIX threads.
>In that case I got an error because build_arm_nofpu/staging_dir/include

this area changed recently. You may need to erase build_* toolchain_*

>didn't exist.  I manually created the directory and restarted the build.
>Things continued without further incident and completed with a tool
>chain.  A quick test seems to indicate the generated cross compiler
>works, checked with a simple "Hello world" compiled after exporting the
>staging_dir/usr/bin.
>
>So, NPTL seems broken for ARM.  I've tried using an old ecos version of

you're better off to ask the uclibc list about the state of NTPL
support.
>sysdep-cancel.h and things reach the point that during the gcc-final
>stage libgomp blows up because the pthread library can't be found.  This
>is a configure error saying that pthreads are required for libgomp.  I'd
>say I don't even want libgomp.  Is there an easy way to prevent this
>from even being attempted?  I'm thinking of some additional build flag I
>can pass in to buildroot.

See menuconfig. ()  Additional gcc options

  reply	other threads:[~2007-06-27 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26  3:04 [Buildroot] Problem building latest arm michael.miller at prga.com
2007-06-26  6:21 ` Bernhard Fischer
2007-06-27 12:45   ` michael.miller at prga.com
2007-06-27 16:20     ` Bernhard Fischer [this message]
2007-06-29  5:16       ` michael.miller at prga.com
2007-07-02 12:05         ` michael.miller at prga.com

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=20070627162003.GA8454@aon.at \
    --to=rep.dot.nop@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.