From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from devils.ext.ti.com (devils.ext.ti.com [198.47.26.153]) by arago-project.org (Postfix) with ESMTPS id BAC28529B3 for ; Thu, 12 Mar 2015 14:50:52 +0000 (UTC) Received: from dflxv15.itg.ti.com ([128.247.5.124]) by devils.ext.ti.com (8.13.7/8.13.7) with ESMTP id t2CEoqoJ021425 for ; Thu, 12 Mar 2015 09:50:52 -0500 Received: from DFLE72.ent.ti.com (dfle72.ent.ti.com [128.247.5.109]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id t2CEoo2l021976 for ; Thu, 12 Mar 2015 09:50:51 -0500 Received: from dflp32.itg.ti.com (10.64.6.15) by DFLE72.ent.ti.com (128.247.5.109) with Microsoft SMTP Server id 14.3.224.2; Thu, 12 Mar 2015 09:50:50 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by dflp32.itg.ti.com (8.14.3/8.13.8) with ESMTP id t2CEooJE018693; Thu, 12 Mar 2015 09:50:50 -0500 Date: Thu, 12 Mar 2015 10:50:50 -0400 From: Denys Dmytriyenko To: "Stiffler, Jacob" Message-ID: <20150312145049.GK24885@edge> References: <20150311235329.GD23587@edge> <32B5D12402BE454796026F6AC58AA86E33115ACC@DLEE08.ent.ti.com> <20150312004722.GE23587@edge> <20150312040513.GI23587@edge> <5501902A.4060206@ti.com> <4B26FB5A64EBA14C87266869E037F95814107D47@DFLE09.ent.ti.com> <4B26FB5A64EBA14C87266869E037F95814107E1F@DFLE09.ent.ti.com> <5501A4E0.2050107@ti.com> <20150312144215.GJ24885@edge> <4B26FB5A64EBA14C87266869E037F95814107E91@DFLE09.ent.ti.com> MIME-Version: 1.0 In-Reply-To: <4B26FB5A64EBA14C87266869E037F95814107E91@DFLE09.ent.ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "meta-arago@arago-project.org" Subject: Re: [PATCH] recipes-devtools: New ltp-ddt_1.0.0 recipe X-BeenThere: meta-arago@arago-project.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Arago metadata layer for TI SDKs - OE-Core/Yocto compatible List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 14:50:52 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Yes, I understand that. The question is why LEXLIB is not defined and is it needed along with ltp-scanner? Now, libfl library provides a standard main() stub that calls yylex() externally, which you have to provide for lexical analyser. And since only scan.c provides yylex(), that compile line should be the only one to link against libfl. On Thu, Mar 12, 2015 at 10:43:56AM -0400, Stiffler, Jacob wrote: > 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; meta-arago@arago-project.org > 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' > > > >