All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy MacLeod" <randy.macleod@windriver.com>
To: <oleksandr.s.popovych@globallogic.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: <openembedded-core@lists.openembedded.org>,
	Joshua Watt <JPEW.hacker@gmail.com>
Subject: Re: [OE-core][PATCH v8] expat: Added ptest
Date: Wed, 15 Jul 2020 12:54:06 -0400	[thread overview]
Message-ID: <b4996474-6945-9542-0b73-1eeb1499250c@windriver.com> (raw)
In-Reply-To: <CAKqUGW-3RDNU1SFmy9egAbPv8AEOfGBHWb9o34O0P2TxF3boMA@mail.gmail.com>

On 2020-06-03 8:48 a.m., Oleksandr via lists.openembedded.org wrote:
> Hello Richard, Joshua,
> 
> On Mon, May 11, 2020 at 3:45 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>>
>> ...
>>
>> Thanks, this is definitely getting there. There was only one test
>> failure this time, with meta-mingw:
>>
>> https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/1884
>>
>> I've cc'd Joshua in case he has any insights on this.
> 
> I`ve tested my patch with meta-mingw layer on my host and it seems I
> have fixed the current compilation error, with making some changes to
> meta-mingw (by changing "CMAKE_SYSTEM_NAME" variable to "Windows"
> value during toolchain file generation in
> "recipes-core/expat/expat_%.bbappend" file using a
> "recipes-devtools/cmake/cmake_%.bbappend" file as template). However
> this is only part of a solution, because another error appears next to
> it: gdb-cross-canadian that depends on expat now fails to build,
> because it can not find a proper expat library. It seems that expat
> recipe, which was switched to build with CMake in my patch, does not
> generate output library in proper format (it compiles only
> "libexpat.dll.a", when the current version of expat recipe from
> upstream, that uses Autotools, generates both "libexpat.a" and
> "libexpat.dll.a"). This is such an error that I can not figure out how
> to solve it by myself, so I ask for help.

When I was cleaning up my inbox, I noticed this thread had gone idle.

Ugh, I have no idea about Windows, Joshua any ideas?

> 
> Additionally I would like to ask you: How should I send patches now
> when at least two separate patches with similar purposes should be
> sent to different layers (one for [OE-core] and other for
> [meta-mingw])? Should they be connected with some kind of cover-letter
> or is there another option?

I think that if you just CC the maintainers and mention the dependency
in the commit log or wrapper email, then things will work out.

Thanks for continuing to work on this Oleksandr.
Hopefully v9 will work well and be merged.

../Randy

> 
> Thanks for your attention.
> 
> 
> 
> 


-- 
# Randy MacLeod
# Wind River Linux

  reply	other threads:[~2020-07-15 16:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 16:55 [OE-core][PATCH v8] expat: Added ptest Oleksandr
2020-05-11 12:45 ` Richard Purdie
2020-06-03 12:48   ` Oleksandr
2020-07-15 16:54     ` Randy MacLeod [this message]
2020-07-15 19:57       ` Joshua Watt

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=b4996474-6945-9542-0b73-1eeb1499250c@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=JPEW.hacker@gmail.com \
    --cc=oleksandr.s.popovych@globallogic.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.