public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] chage can't open /etc/passwd [SOLVED]
Date: Tue, 18 Sep 2007 20:47:22 -0500	[thread overview]
Message-ID: <1190166442.15232.6.camel@blackwidow.nbk> (raw)
In-Reply-To: <1190164580.20178.19.camel@blackwidow.nbk>

On Tue, 2007-09-18 at 20:16 -0500, Albert Hopkins wrote:
> No, doesn't work.  I'm going to try downgrading GCC (w/o any
> optimizations), re-compiling shadow with my original CFLAGS and see
> what
> happens. 

# grep ^CFLAGS /etc/make.conf
CFLAGS="-O2 -march=k8 -msse3 -ggdb -pipe -fomit-frame-pointer" 

# gcc-config i686-pc-linux-gnu-4.2.0
# source /etc/profile
# chage -l marduk
chage: can't open password file

# gcc-config i686-pc-linux-gnu-4.1.2
# source /etc/profile
# emerge -1 shadow > /dev/null
# chage -l marduk
Last password change                                    : Sep 18, 2007
Password expires                                        : Nov 17, 2007
Password inactive                                       : never
Account expires                                         : never
Minimum number of days between password change          : 0
Maximum number of days between password change          : 60
Number of days of warning before password expires       : 14

Seems to be a problem with GCC.

--
Albert W. Hopkins

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-09-19  2:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 15:12 [gentoo-user] chage can't open /etc/passwd Albert Hopkins
2007-09-17 17:30 ` Ryan Sims
2007-09-17 19:15   ` Albert Hopkins
2007-09-17 19:48     ` Etaoin Shrdlu
2007-09-17 20:30       ` Albert Hopkins
2007-09-17 21:09         ` Etaoin Shrdlu
2007-09-17 21:37           ` Albert Hopkins
2007-09-17 23:17             ` Norberto Bensa
     [not found]               ` <1190075689.7101.8.camel@blackwidow.nbk>
     [not found]                 ` <20070917231502.lbzd6wg9wwkwccos@mail.bensa.ar>
2007-09-18  2:59                   ` Albert Hopkins
2007-09-18  3:14                     ` Norberto Bensa
2007-09-18  8:14                     ` Etaoin Shrdlu
2007-09-18 14:04                       ` Albert Hopkins
2007-09-18 14:07                       ` Albert Hopkins
2007-09-18 21:27                         ` Albert Hopkins
2007-09-18 23:32                           ` Norberto Bensa
2007-09-18 23:56                             ` Albert Hopkins
2007-09-19  0:56                               ` [gentoo-user] chage can't open /etc/passwd [SOLVED] Albert Hopkins
2007-09-19  1:08                                 ` Norberto Bensa
2007-09-19  1:16                                   ` Albert Hopkins
2007-09-19  1:47                                     ` Albert Hopkins [this message]
2007-09-19  2:01                                       ` Norberto Bensa
2007-09-19  2:33                                         ` Albert Hopkins
2007-09-19  2:00                                   ` Steen Eugen Poulsen
2007-09-18  9:05                     ` [gentoo-user] chage can't open /etc/passwd Etaoin Shrdlu
2007-09-17 17:57 ` Etaoin Shrdlu
2007-09-17 20:08 ` Peter Ruskin
2007-09-17 20:32   ` Albert Hopkins

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=1190166442.15232.6.camel@blackwidow.nbk \
    --to=marduk@letterboxes.org \
    --cc=gentoo-user@lists.gentoo.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