The file ./include/mk/config.mk.default makes sure that LEXLIB is undefined.
The meta-oe version of the recipe for v 0.0.4 has a custom configure stage to
make sure that ./include/mk/config.mk.default is the config.mk used:
do_configure() {
cp ${S}/include/config.h.default ${S}/include/config.h
cp ${S}/include/mk/config.mk.default ${S}/include/mk/config.mk
cp ${S}/include/mk/features.mk.default ${S}/include/mk/features.mk
echo "${TAG}" > ${S}/ChangeLog
}
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Stiffler, Jacob
Sent: Thursday, March 12, 2015 10:44 AM
To: Dmytriyenko, Denys; Hernandez, Carlos
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH] recipes-devtools: New ltp-ddt_1.0.0 recipe
The warning implies that LEXLIB is not defined. Therefore LEXLIB should not be
linked for all targets in pan/Makefile, only ltp-scanner.
-----Original Message-----
From: Dmytriyenko, Denys
Sent: Thursday, March 12, 2015 10:42 AM
To: Hernandez, Carlos
Cc: Stiffler, Jacob; [email protected]
Subject: Re: [meta-arago] [PATCH] recipes-devtools: New ltp-ddt_1.0.0 recipe
The successful build doesn't have -lfl after the ltp-scanner skip warning.
On Thu, Mar 12, 2015 at 10:38:24AM -0400, Carlos Hernandez wrote:
> On 03/12/2015 10:21 AM, Stiffler, Jacob wrote:
> >The symbol 'yylex' comes from a flex generated file. Not sure how this isn't
> >being seen in all builds... This will need to link with a flex generated
> >file. In this case, all I can see is scan.c, which is generated from scan.l.
> >So should ltp_bump link with scan.o? If not, then why would ltp-bump need to
> >link with libfl.so?
> >
> >Can you find the log for linking 'ltp-bump' in one of the successful builds?
>
> *14:59:13* make[1]: Entering directory
> `/scratch/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/ltp-ddt/pan'
> *14:59:13*
> /scratch/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/ltp-ddt/pan/Makefile:43:
> ltp-scanner will not be built because a working copy of lex was not found
> *14:59:13*
> /home/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/integration/toolchain/linaro-4.7/bin/arm-linux-gnueabihf-gcc
> -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -W -g -O2
> -Wold-style-definition -D_FORTIFY_SOURCE=2 -Wno-error
> -I/scratch/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/ltp-ddt/pan
> -I../include -I../include -c -o ltp-bump.o ltp-bump.c
> *14:59:13*
> /home/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/integration/toolchain/linaro-4.7/bin/arm-linux-gnueabihf-gcc
> -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -W -g -O2
> -Wold-style-definition -D_FORTIFY_SOURCE=2 -Wno-error
> -I/scratch/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/ltp-ddt/pan
> -I../include -I../include -c -o zoolib.o zoolib.c
> *14:59:13*
> /home/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/integration/toolchain/linaro-4.7/bin/arm-linux-gnueabihf-gcc
> -L../lib ltp-bump.o zoolib.o -lm -o ltp-bump
> *14:59:13*
> /home/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/integration/toolchain/linaro-4.7/bin/arm-linux-gnueabihf-gcc
> -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -W -g -O2
> -Wold-style-definition -D_FORTIFY_SOURCE=2 -Wno-error
> -I/scratch/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/ltp-ddt/pan
> -I../include -I../include -c -o ltp-pan.o ltp-pan.c
> *14:59:14*
> /home/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/integration/toolchain/linaro-4.7/bin/arm-linux-gnueabihf-gcc
> -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -W -g -O2
> -Wold-style-definition -D_FORTIFY_SOURCE=2 -Wno-error
> -I/scratch/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/ltp-ddt/pan
> -I../include -I../include -c -o splitstr.o splitstr.c
> *14:59:14*
> /home/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/integration/toolchain/linaro-4.7/bin/arm-linux-gnueabihf-gcc
> -L../lib ltp-pan.o zoolib.o splitstr.o -lm -o ltp-pan
> *14:59:14* make[1]: Leaving directory
> `/scratch/lcpdbld/jenkins_ws/workspace/start-ltp-ddt-next-build/ltp-ddt/pan'
>
>
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
