From: Dan Malek <dan@netx4.com>
To: Claude Robitaille <crobitaille@videotron.ca>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Compiling 2.3.18
Date: Mon, 20 Sep 1999 00:07:06 -0400 [thread overview]
Message-ID: <37E5B2EA.9C266862@netx4.com> (raw)
In-Reply-To: Pine.LNX.4.10.9909191611110.1836-100000@localhost.localdomain
Claude Robitaille wrote:
> I have no success at compiling (actually just doing make dep) the
> 2.3.18 kernel source I downloaded from linuxppc.cs.nmt.edu...
I'll download it and take a look, although this is now out
of date with the CVS tree.
> I downloaded 2.3.18 from edge.kernelnotes.org and I am able to compile
> (after fixing one of the Config.in file).
This looks like a mirror, so it is likely up to date. What
was the problem with Config.in?
> Could it be a problem with Dave's tar (as for fadsrom.tar)?
I don't understand why some people have problems with this file.
I continually download and extract it just fine on any of my
Linux machines. What are you using?
> I am targetting a board with an MPC8xx, does the source from the
> embedded tree at linuxppc.cs.nmt.edu better....
I usually put something there as a convenience for people that
can't get CVS access through a fire wall. It represents my
source tree, which is known to build, just before I make CVS commits.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-20 4:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-19 20:37 Compiling 2.3.18 Claude Robitaille
1999-09-20 4:07 ` Dan Malek [this message]
1999-09-21 1:18 ` Claude Robitaille
1999-09-22 0:13 ` Claude Robitaille
1999-09-22 1:33 ` Dan Malek
1999-09-22 2:10 ` Claude Robitaille
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=37E5B2EA.9C266862@netx4.com \
--to=dan@netx4.com \
--cc=crobitaille@videotron.ca \
--cc=linuxppc-embedded@lists.linuxppc.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 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).