Daten verschluesseln: cfs kompilieren

Jan-Benedict Glaw jbglaw at lug-owl.de
Mon Aug 14 01:27:05 CEST 2000


On Sun, Aug 13, 2000 at 04:36:43PM +0200, Christian Horn wrote:
> > > Das Problem: cfs lässt sich bei mir leider nicht komilieren. Probierte die
> > 
> > Fehlermeldung? Ich hab' leider meine Glaskugel schon wieder verlegt udn
> > kann deshalb im Moment nicht hellsehen;(
> 
> Das ist ein Argument :)
> Also hier die (längste) Kompilierungs-ausgabe.
> *undef*:1: warning: undefining `__STDC__'
> In file included from /usr/include/sys/un.h:24,
>                  from /usr/include/rpc/clnt.h:44,
>                  from /usr/inclurpcgen -b -c -o nfsproto_xdr.c nfsproto.x 

Viele viele bunte Smarties^WFehler...

Was ist denn das für eine Kernel-Source (bzw. wozu gehören die Dateien
unter /usr/include/linux/)? Sowas kenn' ich von kaputten Entwickler-
Kerneln von vor etwa 2 bis 3 Monaten...

MfG, JBG

-- 
Fehler einges                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       From mutt-users-owner-chr.ordig=gmx.net at ns.gbnet.net Mon Aug 14 02:00:33 2000
Return-Path: <mutt-users-owner-chr.ordig=gmx.net at ns.gbnet.net>
X-Flags: 0000
Delivered-To: GMX delivery to chr.ordig at gmx.net
Received: (qmail 9021 invoked by uid 0); 14 Aug 2000 02:00:33 -0000
Received: from agent57.gbnet.net (194.70.126.12)
  by mx12.rz2.gmx.net with SMTP; 14 Aug 2000 02:00:33 -0000
Received: (qmail 29787 invoked from network); 14 Aug 2000 02:00:33 -0000
Received: from ns.gbnet.net (qmailr at 194.70.126.10)
  by agent57.gbnet.net with SMTP; 14 Aug 2000 02:00:33 -0000
Received: (qmail 15164 invoked by uid 610); 14 Aug 2000 01:58:14 -0000
Received: (qmail 14334 invoked from network); 14 Aug 2000 01:55:25 -0000
Received: from ford.gbnet.org (192.188.96.10)
  by ns.gbnet.net with SMTP; 14 Aug 2000 01:55:25 -0000
Received: (qmail 8381 invoked from network); 14 Aug 2000 01:51:37 -0000
Received: from rdu25-12-060.nc.rr.com (HELO rr.com) (24.25.12.60)
  by ford.gbnet.org with SMTP; 14 Aug 2000 01:51:37 -0000
Received: (from rhh at localhost)
	by rr.com (8.9.3/8.9.3) id VAA08091
	for mutt-users at mutt.org; Sun, 13 Aug 2000 21:57:53 -0400 (EDT)
	(envelope-from aa8vb at nc.rr.com)
Date: Sun, 13 Aug 2000 21:57:53 -0400
From: Randall Hopper <aa8vb at nc.rr.com>
To: mutt-users at mutt.org
Subject: send-hooks matching "all" users - how?
Message-ID: <20000813215753.A8005 at -NOJUNK-vislab.epa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
Sender: owner-mutt-users at mutt.org
Precedence: bulk

     Send hooks engage if the pattern matches "any" recipient.  

     How do I construct one that engages only if the pattern matches "all"
recipients.

     For example:

     unset pgp_autoencrypt
     send-hook (jim|john|joe)@home.com "set pgp_autoencrypt"

This will PGP encrypt if jim, john, or joe are in the recipients line, even
if someone else is a recipient that you don't have a key for.  

     I personally want to find this out as I do now when mutt can't find
the key.  But some fellow mutt users just want to automagically forget
encryption and send to all recipients unencrypted, if anyone is a recipient
that they don't have a key for (in other words, if the pattern doesn't
match "all" recipients).

     manual.txt suggests a leading '^', but this doesn't work.  Maybe 
it only works where you can specify a pattern flag, as in:  ^~C \.de$

Thanks for any tips,

Randall

-- 
Randall Hopper
aa8vb at nc.rr.com