From: Pascal Ouyang <xin.ouyang@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cpan.bbclass: Fix CCFLAGS.
Date: Mon, 2 Jul 2012 15:54:48 +0800 [thread overview]
Message-ID: <4FF153C8.2060902@windriver.com> (raw)
In-Reply-To: <4FEC807C.1040803@gmail.com>
On 2012年06月29日 00:04, Khem Raj wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 6/28/2012 12:59 AM, Pascal Ouyang wrote:
>> On 2012年06月21日 23:47, Khem Raj wrote:
>>> On Thu, Jun 21, 2012 at 12:13 AM, <xin.ouyang@windriver.com>
>>> wrote:
>>>> From: Xin Ouyang <Xin.Ouyang@windriver.com>
>>>>
>>>> We should not just replace CCFLAGS with CFLAGS while compiling,
>>>> because this may cause run-time errors with perl's
>>>> DynaLoader.pm.
>>>>
>>>> Tested on qemux86 with new libnet-libidn-perl bb recipe:
>>>
>>> can you instead try the patch from
>>>
>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=19;bug=628522
>>>
>> This debian patch takes no effect.
>>
>> Actually it try to fix this:
>>
>> Some packages which has those lines in Makefile.PL: WriteMakefile(
>> ... 'CCFLAGS' => 'some cflags', ... ); While run perl
>> Makefile.PL to configure, there are CCFLAGS="some cflags" to
>> override the original CCFLAGS=$Config{ccflags} in generated
>> Makefiles.
>>
>>
>> In Poky, CCFLAGS in our generated Makefiles are all right. But when
>> we run oe_runmake CCFLAGS="${CFLAGS}" to do_compile, this will
>> override our right CCFLAGS.
>
> but thats what assign operator is meant to do isnt it ?
>
But CCFLAGS cannot be overrided by CFLAGS, because original CCFLAGS has
some -DXXX flags read from the config for perl.
Without these compile flags, the perl modules cannot run correctly.
root@qemux86:~# perl -e "use Net::LibIDN"
...
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
-P
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk/sgHwACgkQuwUzVZGdMxSvoACdHtcMLShjJIglhq/KXuE73QIW
> 7FsAoI/IFxzDXZWX/xLj3tNkDDzdUM++
> =MWVl
> -----END PGP SIGNATURE-----
>
--
- Pascal
next prev parent reply other threads:[~2012-07-02 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 7:13 [PATCH] cpan.bbclass: Fix CCFLAGS xin.ouyang
2012-06-21 15:47 ` Khem Raj
2012-06-28 7:59 ` Pascal Ouyang
2012-06-28 16:04 ` Khem Raj
2012-07-02 7:54 ` Pascal Ouyang [this message]
2012-07-05 11:17 ` Pascal Ouyang
2012-07-05 14:57 ` Khem Raj
2012-07-06 5:33 ` Pascal Ouyang
2012-07-06 5:39 ` Khem Raj
2012-07-12 6:46 ` Pascal Ouyang
2012-07-17 16:16 ` Saul Wold
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=4FF153C8.2060902@windriver.com \
--to=xin.ouyang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox