linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@shiny.it>
To: LinuxPPC-dev <linuxppc-dev@lists.linuxppc.org>
Subject: 2.4.22p10 compile error
Date: Thu, 7 Aug 2003 23:27:37 +0000	[thread overview]
Message-ID: <20030807232737.20df47f2.pochini@shiny.it> (raw)


The stable linuxppc_2_4 tree at mvista doesn't compile. make dep fails
very soon:


make _sfdep_chrp _sfdep_pmac _sfdep_prep _FASTDEP_ALL_SUB_DIRS="chrp pmac prep"
make[4]: Entering directory `/opt/KernelSrc/l/arch/ppc/boot/prep'
make -C chrp fastdep
make: Entering an unknown directory
make: *** chrp: No such file or directory.  Stop.
make: Leaving an unknown directory
make[4]: *** [_sfdep_chrp] Error 2
make[4]: Leaving directory `/opt/KernelSrc/l/arch/ppc/boot/prep'
make[3]: *** [fastdep] Error 2
make[3]: Leaving directory `/opt/KernelSrc/l/arch/ppc/boot/prep'
make[2]: *** [_sfdep_prep] Error 2
make[2]: Leaving directory `/opt/KernelSrc/l/arch/ppc/boot'
make[1]: *** [fastdep] Error 2
make[1]: Leaving directory `/opt/KernelSrc/l/arch/ppc/boot'
make: *** [archdep] Error 2
[root@Jay l]#


I also tested the official 2.4.22p10 at kernel.org and it works fine, but the
ethernet.
I have a dual G4mdd, gcc 2.95.4 (YDL2.3).
I would like to try linux 2.6. Do I need to upgrade libc and other stuff ?


--
Bye.
   Giuliano.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-08-07 23:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 23:27 Giuliano Pochini [this message]
2003-08-08 17:03 ` 2.4.22p10 compile error Tom Rini
2003-08-08 17:12   ` Benjamin Herrenschmidt
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=20030807232737.20df47f2.pochini@shiny.it \
    --to=pochini@shiny.it \
    --cc=linuxppc-dev@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).