public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clum at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/15389] Error when compiling anything on Knoppix
Date: Sat, 29 Oct 2005 17:57:00 -0000	[thread overview]
Message-ID: <20051029175741.26886.qmail@sourceware.org> (raw)
In-Reply-To: <bug-15389-8515@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from clum at users dot sourceforge dot net  2005-10-29 17:57 -------
This is really weird. I have used gcc many, many times, (but never on Knoppix
before) and have never had such a problem. I'm having the exact same problem.
It happens right away when I compile, even if I only do preprocessing with -E.
It works fine if I su into root. But I have full permissions on the file and
directory I'm doing it in (/home/knoppix). I'm running a Dell Dimension 8100
with a P4 processor and Knoppix 4.0.2. I just tried an experiment and got it to
work with user knoppix as well. What I had to do was set a password for user
knoppix. If I tried passwd directly in knoppix, it asks for the current
password, which doesn't exist, so I can't change it, but if I su, and then
passwd knoppix, and enter a new password, and exit, then gcc works fine. This
Knoppix comes with gcc 3.3.6.


-- 

clum at users dot sourceforge dot net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clum at users dot
                   |                            |sourceforge dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15389


       reply	other threads:[~2005-10-29 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15389-8515@http.gcc.gnu.org/bugzilla/>
2005-10-29 17:57 ` clum at users dot sourceforge dot net [this message]
2004-05-12 19:29 [Bug c/15389] New: " submerged_one at yahoo dot com
2004-05-12 20:03 ` [Bug c/15389] " falk at debian dot org

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=20051029175741.26886.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).