public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: /bin/sh: line 1: defkeymap.c: Permission denied (2.4-BK)
Date: Wed, 02 Jun 2004 16:38:50 +0200	[thread overview]
Message-ID: <40BDE67A.9030402@g-house.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi,

every now and then i get an error when trying to compile 2.4 kernels.
to see what's going on i just moved drivers/char/defkeymap.* to
somewhere else and did the following:


- ---------------------------------
$ la drivers/char/defkeymap.*
ls: drivers/char/defkeymap.*: No such file or directory
$ bk co drivers/char/defkeymap.c
drivers/char/defkeymap.c 1.1: 262 lines
$ bk co drivers/char/defkeymap.map
drivers/char/defkeymap.map 1.1: 357 lines
$ la drivers/char/defkeymap.*
- -r--r--r--    1 evil users  11K Jun  2 16:26 drivers/char/defkeymap.c
- -r--r--r--    1 evil users  12K Jun  2 16:26 drivers/char/defkeymap.map

$ make bzImage 2>&1 | tail -n10
make[3]: Entering directory `/usr/src/linux-2.4-BK/drivers/char'
set -e ; loadkeys --mktable defkeymap.map | sed -e 's/^static *//' >
defkeymap.c
/bin/sh: line 1: defkeymap.c: Permission denied
make[3]: *** [defkeymap.c] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4-BK/drivers/char'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4-BK/drivers/char'
make[1]: *** [_subdir_char] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4-BK/drivers'
make: *** [_dir_drivers] Error 2
$ umask
0022
- ---------------------------------

i'll chmod drivers/char/defkeymap.c to 0644 then and it's compiling
then. i can also *ignore* the error ("make -i") and the kernel will
build fine. how comes? and why is the file 0444 at all?

Thanks,
Christian.

PS: this is debian/unstable (i386), with
$ gcc --version
gcc (GCC) 3.3.3 (Debian 20040422)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ ld -V
GNU ld version 2.14.90.0.7 20031029 Debian GNU/Linux
~  Supported emulations:
~   elf_i386
~   i386linux
~   elf_x86_64
- --
BOFH excuse #377:

Someone hooked the twisted pair wires into the answering machine.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAveZ6+A7rjkF8z0wRAooXAJwLyxauqZ6Sb8TN3r3W0pkOZ/uiLgCfaCOI
MGQkz3B3ilygOL9pA3alviw=
=cpN3
-----END PGP SIGNATURE-----

                 reply	other threads:[~2004-06-02 14:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40BDE67A.9030402@g-house.de \
    --to=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.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