From: "John (Eljay) Love-Jensen" <eljay@adobe.com>
To: Niklaus <niklaus@gmail.com>, GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: Search path directory limit
Date: Fri, 19 Dec 2008 15:51:00 -0000 [thread overview]
Message-ID: <C5710F24.36B46%eljay@adobe.com> (raw)
In-Reply-To: <85e0e3140812190617rf233761ie37a165793d4c838@mail.gmail.com>
Hi Nik,
> Can we restrict the paths from which gcc includes the header files.
No, I do not believe anyone has added that kind of functionality to the
preprocessor.
If you want, you can submit a patch to cpp with that feature.
> Can we tell gcc on a command line parameters/makefile to not include anything
from "/dev" ?
No, I do not believe anyone has added that kind of functionality to GNU Make
or GCC.
If you want, you can submit a patch to GCC and/or GNU Make with that
feature.
> Removing read access on those devices are not possible.
Depends on the operating system. Using ACLs I was able to prohibit myself
from accessing /dev/random. I probably could prohibit myself by chmod'ing
the UGO bits. Also consider chroot (or jail), quotas and ulimit.
HTH,
--Eljay
next prev parent reply other threads:[~2008-12-19 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 14:44 Niklaus
2008-12-19 15:51 ` John (Eljay) Love-Jensen [this message]
2008-12-19 16:48 ` Ian Lance Taylor
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=C5710F24.36B46%eljay@adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=niklaus@gmail.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).