From: Richard Cochran <richardcochran@gmail.com>
To: Peter Foley <pefoley2@pefoley.com>
Cc: David Daney <ddaney.cavm@gmail.com>,
David Miller <davem@davemloft.net>,
markos.chandras@imgtec.com, linux-mips@linux-mips.org,
corbet@lwn.net, netdev@vger.kernel.org,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: ptp: Fix build failure on MIPS cross builds
Date: Wed, 22 Oct 2014 10:03:02 +0200 [thread overview]
Message-ID: <20141022080302.GA4037@localhost.localdomain> (raw)
In-Reply-To: <CAOFdcFNYHgupvMChb4NedMsUMAOmE8k0D_F5eRjL-8H8ft=eRw@mail.gmail.com>
On Tue, Oct 21, 2014 at 06:04:51PM -0400, Peter Foley wrote:
> The intention of these changes was to generate more compiliation
> coverage for code in Documentation/
Sounds good.
> The underlying issue is that this doesn't work for cross-compiling
> because kbuild doesn't have cross-compile support for userspace code.
Well, my testptp does cross compile just fine. All it needs is the glibc
library bundled with the tool chain and the kernel headers.
> I submitted a patch to disable building Documentation when
> cross-compiling, as the consensus in the thread that resulted in that
> patch (https://lkml.org/lkml/2014/10/8/510) was that implementing
> targetprogs in kbuild was not currently worth it.
So this patch did not make it in, right?
Otherwise people wouldn't be disabling cross compilation ad hoc, like
in the patch that started this thread.
> I can try to take a crack at adding targetprogs support, but I'm
> rather busy right now, so it may take a little while.
No rush, please do.
In the mean time, I would like to restore the testptp.mk that *does*
cross compile, so that people may use the test program if they
want. In fact I use this all the time, and so I am a bit annoyed that
something working was deleted and replaced with something broken.
Thanks,
Richard
next prev parent reply other threads:[~2014-10-22 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 8:42 [PATCH] Documentation: ptp: Fix build failure on MIPS cross builds Markos Chandras
2014-10-21 11:07 ` Richard Cochran
2014-10-21 12:11 ` Markos Chandras
2014-10-21 12:52 ` Richard Cochran
2014-10-21 13:03 ` Markos Chandras
2014-10-21 13:39 ` Richard Cochran
2014-10-21 16:35 ` David Miller
2014-10-21 16:58 ` David Daney
2014-10-21 18:27 ` Richard Cochran
2014-10-21 22:04 ` Peter Foley
2014-10-22 8:03 ` Richard Cochran [this message]
2014-10-22 14:09 ` Peter Foley
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=20141022080302.GA4037@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ddaney.cavm@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=netdev@vger.kernel.org \
--cc=pefoley2@pefoley.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 NNTP newsgroup(s).