From: "Sebastian Werner" <sebastian@werner-productions.de>
To: <gentoo-dev@cvs.gentoo.org>
Subject: AW: AW: [gentoo-dev] gcc 3.0.2 system build notes
Date: Thu, 15 Nov 2001 17:48:06 +0100 [thread overview]
Message-ID: <000001c16df5$4d28d020$0100a8c0@wp> (raw)
In-Reply-To: <3BF2E82B.9000409@acm.org>
Emacs is a problem for pam? I don’t know why?
When I bootstrap a new system and then merge the system. Emacs wouldn't
be installed. OK, e3 is a link. But what has pam to-do with emacs?
Please tell me a solution... (if you know) Thanks
Sebastian
-----Ursprüngliche Nachricht-----
Von: gentoo-dev-admin@cvs.gentoo.org
[mailto:gentoo-dev-admin@cvs.gentoo.org] Im Auftrag von Chad Huneycutt
Gesendet: Mittwoch, 14. November 2001 22:55
An: gentoo-dev@cvs.gentoo.org
Betreff: Re: AW: [gentoo-dev] gcc 3.0.2 system build notes
Sebastian Werner wrote:
>I think you get the pam error with any option in make.conf. I thought
>It was a problem only on my system, but it seems to be not. I use
>The pam and pwdb binary-packages form rc5. - ok this is not very clean
>But work for me!
>
Check your /usr/bin/emacs. I *think* that is what caused this problem
(I may be confused). When configure looks for emacs, it just looks to
see if the 'emacs' is in the path, not if emacs is actually installed.
The problem is that /usr/bin/emacs is a link to e3em on some systems,
and this causes confuses configure (I can explain more if anyone is
interested). This may not be the problem here, but it is for some other
packages.
Chad
_______________________________________________
gentoo-dev mailing list
gentoo-dev@cvs.gentoo.org
http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2001-11-15 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 12:18 [gentoo-dev] gcc 3.0.2 system build notes Grant Goodyear
2001-11-14 15:31 ` AW: " Sebastian Werner
2001-11-14 15:54 ` Chad Huneycutt
2001-11-15 16:48 ` Sebastian Werner [this message]
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='000001c16df5$4d28d020$0100a8c0@wp' \
--to=sebastian@werner-productions.de \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@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