From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/atngw100
Date: Wed, 26 Sep 2007 23:02:46 +0200 [thread overview]
Message-ID: <20070926210246.GB20951@aon.at> (raw)
In-Reply-To: <20070920164416.41018A658C@busybox.net>
On Thu, Sep 20, 2007 at 09:44:16AM -0700, ulf at uclibc.org wrote:
>Author: ulf
>Date: 2007-09-20 09:44:15 -0700 (Thu, 20 Sep 2007)
>New Revision: 19912
>
>Log:
>Enable CONFIG_SEQ in busybox for ngw100
>
>Modified:
> trunk/buildroot/target/device/Atmel/atngw100/busybox-1.6.1.config
That's interresting. atngw100_defconfig doesn't build for me since at
least some hundred revisions.
Can you please show me the exact commands that are ment to build this
config?
PS: In fact, what ATMEL defconfig can i use as a reference if *any*
of these ATMEL targets is building successfully?
next prev parent reply other threads:[~2007-09-26 21:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 16:44 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/atngw100 ulf at uclibc.org
2007-09-26 21:02 ` Bernhard Fischer [this message]
2007-09-26 21:09 ` [Buildroot] svncommit: trunk/buildroot/target/device/Atmel/atngw100 Jonathan Dumaresq
2007-09-27 0:27 ` [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/atngw100 Ulf Samuelsson
2007-09-27 3:00 ` Thiago A. Corrêa
-- strict thread matches above, loose matches on Subject: below --
2009-01-31 20:43 ulf at uclibc.org
2009-01-11 21:15 ulf at uclibc.org
2009-01-06 23:02 ulf at uclibc.org
2008-07-04 10:36 ulf at uclibc.org
2008-07-02 15:43 correa at uclibc.org
2007-10-23 23:01 ulf at uclibc.org
2007-10-12 15:16 ulf at uclibc.org
2007-10-01 21:16 ulf at uclibc.org
2007-09-29 20:47 ulf at uclibc.org
2007-09-27 0:19 ulf at uclibc.org
2007-09-12 4:40 ulf at uclibc.org
2007-08-17 13:17 ulf at uclibc.org
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=20070926210246.GB20951@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox