All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ni Qingliang <niqingliang@insigma.com.cn>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: ntpclient compile fail
Date: Wed, 28 Sep 2011 10:33:22 +0800	[thread overview]
Message-ID: <1317177214.6536.113.camel@localhost.localdomain> (raw)
In-Reply-To: <CAEsOVNey3Ncnzw+wyJcvhPWO89Vbs0PrVB+pTwsJLht3xS-3og@mail.gmail.com>

thanks.

If we want to use the original Makefile, we must get rid of the "-e" and
"-Wl,as-needed" in original arguments, for latter, we can add
"-Wl,--no-as-needed", but what about the "-e"?

On Wed, 2011-09-28 at 10:12 +0800, McClintock Matthew-B29882 wrote:
> On Tue, Sep 27, 2011 at 9:04 PM, Ni Qingliang
> <niqingliang@insigma.com.cn> wrote:
> > 1. sorry, I will.
> > 2. Yes, I made a new Makefile (based on the original) as the patch of
> > ntpclient (which will override the original Makefile).
> 
> There are lots of ways to do this and avoid making a patch. You can
> use EXTRA_OECONF, EXTRA_OEMAKE, EXTRA_CFLAGS, etc in the recipe itself
> to fix up the build process. You can even go and modify the variables
> in the do_configure, do_compile, etc build steps as well.
> 
> -M

-- 
Yi Qingliang
niqingliang@insigma.com.cn
http://niqingliang2003.wordpress.com




      reply	other threads:[~2011-09-28  2:34 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
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 [this message]

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=1317177214.6536.113.camel@localhost.localdomain \
    --to=niqingliang@insigma.com.cn \
    --cc=B29882@freescale.com \
    --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.