[#5598] bluez-utils has parallel build issues with parser.h
Submitted By: Vivi Li
Open Date
2009-10-12 06:22:27 Close Date
2009-10-22 23:25:10
Priority:
Medium Assignee:
Mike Frysinger
Status:
Closed Fixed In Release:
N/A
Found In Release:
2010R1 Release:
Category:
N/A Board:
N/A
Processor:
ALL Silicon Revision:
Is this bug repeatable?:
Yes Resolution:
Fixed
Uboot version or rev.:
Toolchain version or rev.:
gcc4.1-09r1-rc9
App binary format:
N/A
Summary: bluez-utils has parallel build issues with parser.h
Details:
Build application BLUEZ, sometimes it will fail to build due to missing parser.h. parser.h must be generated before kword.c is compiled.
To reproduce this bug, remove build-bluez-utils-2.25 first, then build kernel with BLUEZ application without single mode.
Bellow is the log:
--
bfin-uclinux-gcc -DHAVE_CONFIG_H -I. -I../../bluez-utils-2.25/hcid -I.. -I../../bluez-utils-2.25/common -DEMBED -D__uClinux__ -I/home/test/work/cruise/checkouts/uclinux-dist -mcpu=bf537-0.2 -DDBUS_API_SUBJECT_TO_CHANGE -pipe -Wall -g -O2 -mcpu=bf537-0.2 -D_FORTIFY_SOURCE=2 -c `test -f '../../bluez-utils-2.25/hcid/kword.c' || echo '../../bluez-utils-2.25/hcid/'`../../bluez-utils-2.25/hcid/kword.c
sed '/^#/ s|lex.yy\.c|lexer.c|' lex.yy.c >lexer.c
rm -f lex.yy.c
../../bluez-utils-2.25/hcid/kword.c:42:20: error: parser.h: No such file or directory
../../bluez-utils-2.25/hcid/kword.c:45: error: ‘K_OPTIONSâ€
undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:46: error: ‘K_DEVICE†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:48: error: ‘K_AUTOINIT†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:49: error: ‘K_SECURITY†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:50: error: ‘K_PAIRING†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:51: error: ‘K_PTYPE†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:52: error: ‘K_LM†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:53: error: ‘K_LP†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:54: error: ‘K_ISCAN†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:55: error: ‘K_PSCAN†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:56: error: ‘K_NAME†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:57: error: ‘K_CLASS†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:58: error: ‘K_VOICE†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:59: error: ‘K_INQMODE†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:60: error: ‘K_PAGETO†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:61: error: ‘K_AUTH†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:62: error: ‘K_ENCRYPT†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:63: error: ‘K_PINHELP†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:64: error: ‘K_DBUSPINHELP†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:66: error: ‘K_YES†undeclared here (not in a function)
../../bluez-utils-2.25/hcid/kword.c:67: error: ‘K_NO†undeclared here (not in a function)
if test -f y.tab.h; then \
to=`echo "parser_H" | sed \
-e 'y/abcdefghijklmnopqrstuvwxyz/ABCDEFGHIJKLMNOPQRSTUVWXYZ/' \
-e 's/[^ABCDEFGHIJKLMNOPQRSTUVWXYZ]/_/g'`; \
sed "/^#/ s/Y_TAB_H/$to/g" y.tab.h >parser.ht; \
rm -f y.tab.h; \
if cmp -s parser.ht parser.h; then \
rm -f parser.ht
else \
mv parser.ht parser.h; \
fi; \
fi
make[5]: *** [kword.o] Error 1
make[5]: *** Waiting for unfinished jobs....
if test -f y.output; then \
mv y.output parser.output; \
fi
sed '/^#/ s|y\.tab\.c|parser.c|' y.tab.c >parser.ct && mv parser.ct parser.c
rm -f y.tab.c
make[5]: Leaving directory `/home/test/work/cruise/checkouts/uclinux-dist/user/bluez-utils/build-bluez-utils-2.25/hcid'
make[4]: *** [install-recursive] Error 1
--
Follow-ups
--- Mike Frysinger 2009-10-22 04:15:09
should be fixed now by including the generated lexer/parser in the dist.
packages should be doing this anyways -- no point in regenerating this on every
build host since the result should always be the same.
Files
Changes
Commits
Dependencies
Duplicates
Associations
Tags
File Name File Type File Size Posted By
No Files Were Found