Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: qemu: fails to build without zlib-dev installed on buildhost
Date: Tue, 16 Mar 2010 13:15:27 -0700	[thread overview]
Message-ID: <19c1b8a91003161315i577fe8b7ne7228be1696902a9@mail.gmail.com> (raw)
In-Reply-To: <201003160004.24164.roman@khimov.ru>

2010/3/15 Roman I Khimov <roman@khimov.ru>:
> В сообщении от Понедельник 15 марта 2010 18:58:45 автор Thomas Zimmermann
> написал:
>> Please check the following patch, as i've no exprience with
>> BBCLASSEXTEND="native" and i don't want to break qemu.
>
> Thanks for reporting, first of all.
>
>> -DEPENDS = "zlib"
>> +DEPENDS = "zlib-native"
>
> zlib-native is already a dependency for qemu-native thanks to BBCLASSEXTEND
> magic.
>
>>  do_configure() {
>> +       export QEMU_CFLAGS="-I${STAGING_INCDIR_NATIVE} ${QEMU_CFLAGS}"
>>         ${S}/configure --prefix=${prefix} ${EXTRA_OECONF}
>>  }
>
> And this one should only be added for native.

IMO this part seems appropriate for BBCLASSEXTEND also. Its common enough

>
> So I think something like attached patch should be a bit better. Please try
> that.
>
> --
>  http://roman.khimov.ru
> mailto: roman@khimov.ru
> gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>



      parent reply	other threads:[~2010-03-16 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 15:58 qemu: fails to build without zlib-dev installed on buildhost Thomas Zimmermann
2010-03-15 21:04 ` Roman I Khimov
2010-03-16 19:48   ` Roman I Khimov
2010-03-16 20:15   ` Khem Raj [this message]

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=19c1b8a91003161315i577fe8b7ne7228be1696902a9@mail.gmail.com \
    --to=raj.khem@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