All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Noé SERRES" <noe.serres@gmail.com>
To: Linuxppc-embedded@ozlabs.org
Subject: "argument list too long"
Date: Tue, 3 Jan 2006 15:06:40 +0100	[thread overview]
Message-ID: <f8bc181b0601030606x3b29ee28q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

Hi,

I'm trying to compile a kernel for an embedded-powerpc-linux application.
As a first step/training, I followed closely the instructions of the
document "The DENX U-Boot and Linux Guide" for a TQM8XXL board, that is to
say:

bash$ mrproper
bash$ make TQM823L_config
bash$ make oldconfig
bash$ make dep

After a few minutes of dependency creation, I get the following error
"argument list too long":

scripts/mkdep -- `find
/usr/src/linuxppc_2_4_devel-2005-10-25-1440/include/asm
/usr/src/linuxppc_2_4
_devel-2005-10-25-1440/include/linux
/usr/src/linuxppc_2_4_devel-2005-10-25-1440/include/scsi /usr/s
rc/linuxppc_2_4_devel-2005-10-25-1440/include/net
/usr/src/linuxppc_2_4_devel-2005-10-25-1440/includ
e/math-emu \( -name SCCS -o -name .svn \) -prune -o -follow -name \*.h !
-name modversions.h -print`
 > .hdepend
scripts/mkdep: argument list too long
make: *** [dep-files] Error 2

Can someone help me understand where that comes from?
Does it have something to do with the fact that I work under WinXP + Cygwin?
No need to say that I am a newbie to the Linux world... help me, Wolfgang
:-)

Noe Serres
Midi Ingenierie
Toulouse (FR)

[-- Attachment #2: Type: text/html, Size: 1301 bytes --]

             reply	other threads:[~2006-01-03 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 14:06 Noé SERRES [this message]
2006-01-03 14:17 ` "argument list too long" Wolfgang Denk
2006-01-04 13:08   ` Stefan Eletzhofer
2006-01-04 13:36     ` Wolfgang Denk
2006-01-04 13:53       ` Stefan Eletzhofer

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=f8bc181b0601030606x3b29ee28q@mail.gmail.com \
    --to=noe.serres@gmail.com \
    --cc=Linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.