All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: kaos@ocs.com.au
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org
Subject: 2.4.31 make - path name breakage (perhaps)
Date: Wed, 16 Nov 2005 15:09:04 +0000	[thread overview]
Message-ID: <200511161509.04855.nick@linicks.net> (raw)

Hi Keith,

I googled a bit on this, but the nature of the bug makes it impossible to 
search properly.

I found this out as I was trying to build Netgear router DG834 firmware from 
GPL source, and make dep fails.

The reason is due to the untarred path name that includes () I found.

I tested on virgin kernel 2.4.31 with GNU Make version 3.79.1.

top level directory of kernel source as a test:

linux-2.4.31(test)/

And the errors (with a lot removed) - it does a little first then:

> make mrproper
/bin/sh: -c: line 1: syntax error near unexpected token 
`/home/nick/kernel/linux-2.4.31(t'
...
...
make: *** [mrproper] Error 2

> make dep
/bin/sh: -c: line 1: syntax error near unexpected token 
`/home/nick/kernel/linux-2.4.31(test)'
...
...
make[2]: *** [fastdep] Error 2
make[2]: Leaving directory `/home/nick/kernel/linux-2.4.31(test)/kernel'
make[1]: *** [_sfdep_kernel] Error 2
make[1]: Leaving directory `/home/nick/kernel/linux-2.4.31(test)'
make: *** [dep-files] Error 2



I haven't a clue if this is a 'make' issue or not, but a few tests on other 
source builds ok.

Nick
-- 
http://sourceforge.net/projects/quake2plus/

"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb


             reply	other threads:[~2005-11-16 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 15:09 Nick Warne [this message]
2005-11-16 23:47 ` 2.4.31 make - path name breakage (perhaps) Keith Owens

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=200511161509.04855.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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 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.