From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bug 3977: old autobuild format?
Date: Thu, 03 Apr 2008 01:57:23 -0500 [thread overview]
Message-ID: <47F47FD3.4050807@gmail.com> (raw)
In-Reply-To: <200804021205.00689.loudawgucr@gmail.com>
On 04/02/2008 02:05 PM, Louie Ilievski wrote:
> Nobody has anything? Not even just a quick explanation? I haven't had any
> luck getting help on IRC either.
>
> Koen, considering you're the one who closed all the bugs I've looked at with
> that same resolution, you must know what the reason behind it all is.
>
> Thanks!
>
> On Monday 31 March 2008 05:27:49 pm Louie Ilievski wrote:
>> Hi all,
>>
>> I'm new to OE and have a build failure when trying to build the angstrom
>> 2008.1 for aximx50v, using uclibc. I have the exact compile failure
>> described in bug #3977, however, it got closed like so many others with the
>> same resolution of having an old autobuild format. Can someone tell me
>> what we're talking about here exactly? I haven't been able to find out
>> what has changed and what I need to do to fix these issues.
>>
>> If someone can point me in the right direction I'd be glad to try making
>> the necessary changes to fix this build issue.
>>
>> Thanks,
>>
>> ~Lou
Lou,
Please open a new bug for that specific bb recipie or reopen that bug
with appropriate changes. Koen closed all the old autobuild bugs to let
us use a more concise format for autobuild bugs. It doesn't mean the bug
has been solved or looked into.
Regards
Gordon
next prev parent reply other threads:[~2008-04-03 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 0:27 Bug 3977: old autobuild format? Louie Ilievski
2008-04-02 19:05 ` Louie Ilievski
2008-04-03 6:57 ` Junqian Gordon Xu [this message]
2008-04-03 8:02 ` Graeme Gregory
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=47F47FD3.4050807@gmail.com \
--to=xjqian@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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