public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nwerneck@yahoo.com.br
To: gcc-gnats@gcc.gnu.org
Subject: other/4441: can´t build  "execvp: true: Permission denied"
Date: Tue, 02 Oct 2001 11:26:00 -0000	[thread overview]
Message-ID: <20011002181812.20975.qmail@sourceware.cygnus.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

>Number:         4441
>Category:       other
>Synopsis:       can´t build  "execvp: true: Permission denied"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 02 11:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     nwerneck@yahoo.com.br
>Release:        gcc-3.0.1
>Organization:
>Environment:
intel 486  Debian GNU/Linux
>Description:
I´m trying to build the 3.0.1, but I get this "execvp: true: Permission denied" error message when I 'make' it.

In the start, it was complaininng about "true: Command not found". I din´t have a /bin/true program. So, i created it (#!/bin/sh\nexit 1;), and the make process could go on... But now it is stopping with this error.

Well, I´m not certain this is the place to talk about this... should this problem be corrected with the people from the debian distribution? I simply can´t find where to start some kind of workaround anymore....

Hope I´m not "off-topic"!
>How-To-Repeat:
download gcc-core-3.0.1 and gcc-g++-3.0.1 on a 486 with Debian GNU/Linux, and try to build!
(well, I haven´t tried with any other computers... so, it can be just me :/ )

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-10-02 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-02 11:26 nwerneck [this message]
2001-10-02 14:36 other/4441: can´t " pme

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=20011002181812.20975.qmail@sourceware.cygnus.com \
    --to=nwerneck@yahoo.com.br \
    --cc=gcc-gnats@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).