From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Giuliano Pochini <pochini@shiny.it>,
LinuxPPC-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.22p10 compile error
Date: 08 Aug 2003 19:12:07 +0200 [thread overview]
Message-ID: <1060362726.653.5.camel@gaston> (raw)
In-Reply-To: <20030808170309.GA8475@ip68-0-152-218.tc.ph.cox.net>
> It looks like your copy of the rsync tree is missing files. Please
> update the tree and try again.
My bk clone does that too:
make _sfdep_chrp _sfdep_pmac _sfdep_prep _FASTDEP_ALL_SUB_DIRS="chrp pmac prep"
make[4]: Entering directory `/home/benh/kernels/linuxppc_benh_devel/arch/ppc/boot/prep'
make -C chrp fastdep
make: *** chrp: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[4]: *** [_sfdep_chrp] Error 2
make[4]: Leaving directory `/home/benh/kernels/linuxppc_benh_devel/arch/ppc/boot/prep'
make[3]: *** [fastdep] Error 2
make[3]: Leaving directory `/home/benh/kernels/linuxppc_benh_devel/arch/ppc/boot/prep'
make[2]: *** [_sfdep_prep] Error 2
make[2]: Leaving directory `/home/benh/kernels/linuxppc_benh_devel/arch/ppc/boot'
make[1]: *** [fastdep] Error 2
make[1]: Leaving directory `/home/benh/kernels/linuxppc_benh_devel/arch/ppc/boot'
make: *** [archdep] Error 2
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-08 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 23:27 2.4.22p10 compile error Giuliano Pochini
2003-08-08 17:03 ` Tom Rini
2003-08-08 17:12 ` Benjamin Herrenschmidt [this message]
2003-08-08 17:56 ` Tom Rini
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=1060362726.653.5.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@shiny.it \
--cc=trini@kernel.crashing.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).