From: "Yi Fan Yu" <yifan.yu@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Andrey Zhizhikin <andrey.z@gmail.com>,
hongxu <hongxu.jia@windriver.com>,
Randy MacLeod <randy.macleod@windriver.com>,
"Chen, Qi" <qi.chen@windriver.com>,
Ross Burton <ross@burtonini.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] Help with dealing with autoconf uprev affected packages?
Date: Fri, 5 Feb 2021 09:46:04 -0500 [thread overview]
Message-ID: <86f09202-225b-ceee-ebfd-1f4ad3be20c1@windriver.com> (raw)
In-Reply-To: <CAMKF1sr-fsVGdCegDri4Vy7cJK8AZ18M6X8E76XThfi7C34KLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
libmcrypt still uses autoconf 2.59. last release seems to date from 2007
https://sourceforge.net/projects/mcrypt/files/Libmcrypt/2.5.8/
its not going to be a piece of cake...
On 2/4/21 10:26 PM, Khem Raj wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> We are now left with 15 odd packages
>
> https://errors.yoctoproject.org/Errors/Build/116395/
>
> On Thu, Feb 4, 2021 at 1:47 PM Khem Raj <raj.khem@gmail.com> wrote:
>> here is latest list
>>
>> https://errors.yoctoproject.org/Errors/Build/116365/
>>
>> Just look at the do_configure failures for filtering to autotools issues only.
>>
>> On Thu, Feb 4, 2021 at 1:09 PM Yi Fan Yu <yifan.yu@windriver.com> wrote:
>>> Andrey,
>>>
>>> i am working on this now.
>>>
>>> since you already submitted iperf3, i'll focus on
>>>
>>> libmcrypt.
>>>
>>> i'll test and build both of them once i figure out libmcrypt.
>>>
>>>
>>> On 2/4/21 5:45 AM, Andrey Zhizhikin wrote:
>>>>>> - iperf3 - YiFan
>>>> I just sent a patch for this one:
>>>> https://lists.openembedded.org/g/openembedded-devel/message/89274
>>>>
>>>> YiFan, can you please have a look at it to see if it fits?
>>>>
>>>>
>>>>
>>>>
[-- Attachment #2: Type: text/html, Size: 2718 bytes --]
next prev parent reply other threads:[~2021-02-05 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8f242d61-4dea-070a-217d-657e2204a807@windriver.com>
[not found] ` <CAAnfSTsku9yTFYKCMVkmKq=77V8XGgq9pdO5n_PPb_ttHWnd3w@mail.gmail.com>
2021-02-02 19:17 ` Help with dealing with autoconf uprev affected packages? Randy MacLeod
2021-02-03 3:01 ` Khem Raj
2021-02-04 10:06 ` hongxu
2021-02-04 10:45 ` [oe] " Andrey Zhizhikin
2021-02-04 21:09 ` Yi Fan Yu
2021-02-04 21:47 ` Khem Raj
2021-02-05 3:26 ` Khem Raj
2021-02-05 14:46 ` Yi Fan Yu [this message]
2021-02-05 23:42 ` Randy MacLeod
2021-02-08 18:44 ` Khem Raj
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=86f09202-225b-ceee-ebfd-1f4ad3be20c1@windriver.com \
--to=yifan.yu@windriver.com \
--cc=andrey.z@gmail.com \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=qi.chen@windriver.com \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=ross@burtonini.com \
/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.