diff options
| author | Kevin Tian <kevin.tian@intel.com> | 2010-09-08 16:57:03 +0800 |
|---|---|---|
| committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-09-08 14:39:00 +0100 |
| commit | c519aec68c61ae2a3822fde0c8e4616a97d2faaf (patch) | |
| tree | a06515c46cc3d4886653f223911200254313f5fb /bitbake/lib/bb/fetch | |
| parent | 7892add2de517a0273f64fcd0d398d96531cd5a2 (diff) | |
| download | openembedded-core-c519aec68c61ae2a3822fde0c8e4616a97d2faaf.tar.gz openembedded-core-c519aec68c61ae2a3822fde0c8e4616a97d2faaf.tar.bz2 openembedded-core-c519aec68c61ae2a3822fde0c8e4616a97d2faaf.tar.xz openembedded-core-c519aec68c61ae2a3822fde0c8e4616a97d2faaf.zip | |
libzypp: workaround to pass mips build
libzypp failed due to GCC "internal compiler error: segmentation fault" error on
MIPS target. The cause is about boost tribool type usage. If having assignement
within conditional check as below:
if ( (a = b) )
...
<a is a tribool type, b is a normal bool type>
then gcc4.3.3 throws internal error. Then the workaround is to move assignement
out of the conditional check.
However I didn't find same case from web.
We can come back to recheck this issue after upgrading to gcc4.5.0 for MIPS. If
this issue is still there, we'll need more analysis to decide whether to report
to gcc upstream or to libzypp upstream.
This fixes [BUGID #277]
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Diffstat (limited to 'bitbake/lib/bb/fetch')
0 files changed, 0 insertions, 0 deletions