Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nelson <robert.nelson.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2009.02-rc2 released
Date: Mon, 26 Jan 2009 11:24:28 -0600	[thread overview]
Message-ID: <497DF1CC.2010404@gmail.com> (raw)
In-Reply-To: <87skn9iv5w.fsf@macbook.be.48ers.dk>

On 1/23/2009 3:12 PM, Peter Korsgaard wrote:
> Hi,
>
> Another week, another release candidate. I have released
> buildroot-2009.02-rc2:
>
> http://buildroot.uclibc.org/downloads/buildroot-2009.02-rc2.tar.gz
>
> or
>
> http://buildroot.uclibc.org/downloads/buildroot-2009.02-rc2.tar.bz2
>
> Please give it a spin and report back issues to the mailing list or
> the bug tracker.
>
> I think we're pretty well on track to do a final release in 2 weeks.
>
>    

Hi Peter & Ulf,

Was just able to test rc-2 for avr32 (atngw100_defconfig and friends)

default atngw100_defconfig is failling at this point in rc2...

log***************
make[4]: Entering directory 
`/media/mirror/testing/buildroot-2009.02-rc2/build_avr32/libglib2-2.16.6/gobject'
make[4]: `glib-genmarshal' is up to date.
make[4]: Leaving directory 
`/media/mirror/testing/buildroot-2009.02-rc2/build_avr32/libglib2-2.16.6/gobject'
echo "#ifndef __G_MARSHAL_H__" > xgen-gmh \
&& echo "#define __G_MARSHAL_H__" >> xgen-gmh \
&& /usr/bin/glib-genmarshal --nostdinc --prefix=g_cclosure_marshal 
./gmarshal.list --header >> xgen-gmh \
&& echo "#endif /* __G_MARSHAL_H__ */" >> xgen-gmh \
&& (cmp -s xgen-gmh gmarshal.h 2>/dev/null || cp xgen-gmh gmarshal.h) \
&& rm -f xgen-gmh xgen-gmh~ \
&& echo timestamp > stamp-gmarshal.h
/bin/sh: line 2: /usr/bin/glib-genmarshal: No such file or directory
make[3]: *** [stamp-gmarshal.h] Error 127
make[3]: Leaving directory 
`/media/mirror/testing/buildroot-2009.02-rc2/build_avr32/libglib2-2.16.6/gobject'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory 
`/media/mirror/testing/buildroot-2009.02-rc2/build_avr32/libglib2-2.16.6'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/media/mirror/testing/buildroot-2009.02-rc2/build_avr32/libglib2-2.16.6'
make: *** 
[/media/mirror/testing/buildroot-2009.02-rc2/build_avr32/libglib2-2.16.6/.stamp_built] 
Error 2

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

  parent reply	other threads:[~2009-01-26 17:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 21:12 [Buildroot] 2009.02-rc2 released Peter Korsgaard
2009-01-23 21:27 ` Cyril HAENEL
2009-01-24  9:02   ` Peter Korsgaard
2009-01-24 13:03     ` Cyril HAENEL
2009-01-26 17:24 ` Robert Nelson [this message]
2009-01-26 17:43   ` Peter Korsgaard
2009-01-26 18:30     ` Robert Nelson
2009-01-26 18:49       ` Peter Korsgaard
2009-01-28  8:47 ` Hinko Kocevar
2009-01-28 16:37   ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-01-25  0:28 Paul Jones
2009-01-25  7:32 ` Ulf Samuelsson
2009-01-25 13:07   ` Peter Korsgaard
2009-01-25 21:17     ` Ulf Samuelsson
2009-01-25 21:28       ` Peter Korsgaard
2009-01-25 22:24         ` Ulf Samuelsson
2009-01-25 23:52           ` Paul Jones
2009-01-26  5:54             ` Peter Korsgaard
2009-01-26  8:48               ` Cyril HAENEL
2009-01-26 16:23           ` Peter Korsgaard
2009-01-26 12:04       ` Thomas Lundquist

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=497DF1CC.2010404@gmail.com \
    --to=robert.nelson.work@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