Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] kvmtool: add new package
Date: Sun, 21 Jun 2015 07:28:56 -0300	[thread overview]
Message-ID: <558691E8.5020001@free-electrons.com> (raw)
In-Reply-To: <5585D3D3.4060708@mind.be>

On 20/06/15 17:57, Arnout Vandecappelle wrote:

>   Could you add a hash file?

I didn't know we were adding hashes to git sources, it's bad for a 
couple of reasons.

>>   	source "package/irda-utils/Config.in"
>>   	source "package/iucode-tool/Config.in"
>>   	source "package/kbd/Config.in"
>> +	source "pacakge/kvmtool/Config.in"
>                     ^^
>                     Excuse me? :-)

Yeah, that's what happens when you move a backport into current and 
you're still ill/running a fever.
And it should also belong in System apps rather than Hardware.

>> +	# No MADV_HUGEPAGE define in uClibc(-ng)
>
>   That's weird, it comes from kernel headers and I do see it in
> asm-generic/mman-common.h. But that is not included by sys/mman.h, so you need
> to include asm/mman.h...

I don't think that's correct, it may work, but the madvise manpages says 
that only sys/mman.h is required.
The MADV_ defines in uclibc are in bits/mman.h, like on glibc and musl, 
so basically they're incomplete/old and a patch to uclibc would be the 
correct way to fix this.

>> +comment "kvmtool needs a (e)glibc or musl toolchain"
>> +	depends on BR2_USE_MMU
>> +	depends on !(BR2_TOOLCHAIN_USES_GLIBC || BR2_TOOLCHAIN_USES_MUSL)
>> +	depends on !(BR2_aarch64 || BR2_arm || BR2_armeb)
>
>   This should depend on the supported architectures. Since the arm ones are
> excluded, it would be just BR2_i386 || BR2_mips || BR2_x86_64

Ack.

>> +#KVMTOOL_VERSION = 0fc7018d0be707c3f48fe78ef6276636d7eae65a
>
>   Remove.

Ack.

>   Makefile tells me there's an optional dependency on libgtk3 as well.

Yes, but only for x86, whatever that means (ARCH_HAS_FRAMEBUFFER).
Fixed, though only build tested.
I'll send v2 shortly.
Regards.

  reply	other threads:[~2015-06-21 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 18:29 [Buildroot] [PATCH] kvmtool: add new package gustavo.zacarias at free-electrons.com
2015-06-20 20:57 ` Arnout Vandecappelle
2015-06-21 10:28   ` Gustavo Zacarias [this message]
2015-06-21 12:58     ` Arnout Vandecappelle
  -- strict thread matches above, loose matches on Subject: below --
2015-06-18 18:26 gustavo.zacarias at free-electrons.com

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=558691E8.5020001@free-electrons.com \
    --to=gustavo.zacarias@free-electrons.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