From: Ni Qingliang <niqingliang@insigma.com.cn>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: ntpclient compile fail
Date: Tue, 27 Sep 2011 11:50:11 +0800 [thread overview]
Message-ID: <1317095411.6536.67.camel@localhost.localdomain> (raw)
In-Reply-To: <1317093523.6536.58.camel@localhost.localdomain>
I have added "override" in the head of every CFLAGS/LDFLAGS line, but
error still there.
the link order is a common problem.
-Wl,-lrt ntpclient.o phaselock.o -o ntpclient
should be
ntpclient.o phaselock.o -Wl,-lrt ntpclient
Does poky have some option or some solution for that?
(I build it success on host.)
On Tue, 2011-09-27 at 11:18 +0800, Ni Qingliang wrote:
> Hello:
> I'm adding ntpclient into my distro.
>
> but build fail, reason is the CFLAGS/LDFLAGS in it's Makefile didn't
> take effect.
>
> What can I do?
>
> the original makefile is:
> CFLAGS += -fno-strict-aliasing
> CFLAGS += -std=c89
> CFLAGS += -W -Wall
> CFLAGS += -O2
> CFLAGS += -DENABLE_DEBUG
> CFLAGS += -DENABLE_REPLAY
>
> LDFLAGS += -lrt
>
> all: ntpclient
>
> test: ntpclient
> ./ntpclient -d -r <test.dat
>
> ntpclient: ntpclient.o phaselock.o
>
> ntpclient.o phaselock.o: ntpclient.h
>
> adjtimex: adjtimex.o
>
> clean:
> rm -f ntpclient adjtimex *.o
>
> --
> Yi Qingliang
> niqingliang@insigma.com.cn
> http://niqingliang2003.wordpress.com
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Yi Qingliang
niqingliang@insigma.com.cn
http://niqingliang2003.wordpress.com
next prev parent reply other threads:[~2011-09-27 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 3:18 ntpclient compile fail Ni Qingliang
2011-09-27 3:50 ` Ni Qingliang [this message]
2011-09-27 15:46 ` McClintock Matthew-B29882
2011-09-28 1:00 ` Ni Qingliang
2011-09-28 1:50 ` McClintock Matthew-B29882
2011-09-28 2:04 ` Ni Qingliang
2011-09-28 2:12 ` McClintock Matthew-B29882
2011-09-28 2:33 ` Ni Qingliang
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=1317095411.6536.67.camel@localhost.localdomain \
--to=niqingliang@insigma.com.cn \
--cc=yocto@yoctoproject.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.