From: Denys Dmytriyenko <denys@ti.com>
To: Carlos Hernandez <ceh@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH] recipes-devtools: New ltp-ddt_1.0.0 recipe
Date: Thu, 12 Mar 2015 10:42:15 -0400 [thread overview]
Message-ID: <20150312144215.GJ24885@edge> (raw)
In-Reply-To: <5501A4E0.2050107@ti.com>
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'
>
>
next prev parent reply other threads:[~2015-03-12 14:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 13:13 [PATCH] recipes-devtools: New ltp-ddt_1.0.0 recipe Carlos Hernandez
2015-03-10 16:19 ` Denys Dmytriyenko
2015-03-10 20:48 ` [PATCH v2] " Carlos Hernandez
2015-03-11 23:53 ` [PATCH] " Denys Dmytriyenko
2015-03-12 0:44 ` Hernandez, Carlos
2015-03-12 0:47 ` Denys Dmytriyenko
2015-03-12 4:05 ` Denys Dmytriyenko
2015-03-12 10:59 ` Stiffler, Jacob
2015-03-12 13:10 ` Carlos Hernandez
2015-03-12 13:19 ` Stiffler, Jacob
2015-03-12 14:11 ` Carlos Hernandez
2015-03-12 14:21 ` Stiffler, Jacob
2015-03-12 14:37 ` Stiffler, Jacob
2015-03-12 14:38 ` Carlos Hernandez
2015-03-12 14:42 ` Denys Dmytriyenko [this message]
2015-03-12 14:43 ` Stiffler, Jacob
2015-03-12 14:50 ` Stiffler, Jacob
2015-03-12 14:53 ` Denys Dmytriyenko
2015-03-12 14:57 ` Carlos Hernandez
2015-03-12 14:56 ` Carlos Hernandez
2015-03-12 14:57 ` Stiffler, Jacob
2015-03-12 15:04 ` Denys Dmytriyenko
2015-03-12 14:50 ` Denys Dmytriyenko
2015-03-12 14:23 ` Denys Dmytriyenko
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=20150312144215.GJ24885@edge \
--to=denys@ti.com \
--cc=ceh@ti.com \
--cc=meta-arago@arago-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.