public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Niklaus <niklaus@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Search path directory limit
Date: Fri, 19 Dec 2008 14:44:00 -0000	[thread overview]
Message-ID: <85e0e3140812190617rf233761ie37a165793d4c838@mail.gmail.com> (raw)

hi,

The below program takes a long time to compile (in minutes).  I 've
these small indiviudal .c/.cpp files which i have to compile and
execute. The problem is with rouge "/dev/random or /dev/urandom".
Solutions like limit the process execution time of gcc is not
appealing.

Can we restrict the paths from which gcc includes the header files.
Can we  tell gcc on a command line parameters/makefile to not include
anything from "/dev" ? If possible how to do it ?
Removing read access on those devices are not possible.


$ cat a.c
#include "/dev/random"
#include<stdio.h>
int main()
{
        return 0;
}

regards, Nik

             reply	other threads:[~2008-12-19 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 14:44 Niklaus [this message]
2008-12-19 15:51 ` John (Eljay) Love-Jensen
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=85e0e3140812190617rf233761ie37a165793d4c838@mail.gmail.com \
    --to=niklaus@gmail.com \
    --cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).