From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Nye Liu <nyet@mrv.com>
Subject: Re: [PATCH] crosstool-ng: missing ntp userland MOD_ macros, ecjx.o should use native compiler
Date: Sat, 26 Sep 2009 21:23:00 -0000 [thread overview]
Message-ID: <200909262323.13371.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <20090924103947.GA10587@mrv.com>
Nye,
All,
On Thursday 24 September 2009 12:39:47 Nye Liu wrote:
> # HG changeset patch
> # User nyet@mrv.com
> # Date 1253788137 25200
> # Node ID bf85e2f5ac55100512f26956be251c42f58068a9
> # Parent 16a2eaf5fd778a6e3eb5ec6b8ec3e0d3e2a28bdb
> ntp uses MOD_NANO not ADJ_NANO
> ecjx.cc -> ecjx.o should use native compiler, not cross compiler
It seems that patch fixes two things, one part related to ecjx, the other
part retaed to fixing glibc and exported kernel headers.
Could you split that into two patches, please?
Also, what is the exact reason for the MOD_ macros wrt NTP? The macros are
nowhere to be found, except in the NTP code. I think the following patch
would be a better fit:
http://www.mail-archive.com/pld-cvs-commit@lists.pld-linux.org/msg191184.html
I looked at the latest kernel sources from Linus' git tree, and there is no
MOD_ macros in there either. Do you know the time-realted tree, by chance?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ___ |
| --==< ^_^ >==-- `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
`------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2009-09-26 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 10:39 Nye Liu
2009-09-26 21:23 ` Yann E. MORIN [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=200909262323.13371.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=nyet@mrv.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).