public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Dave Brolley <brolley@redhat.com>
To: wenji.huang@oracle.com
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Building error for latest stap tree
Date: Sat, 27 Dec 2008 14:27:00 -0000	[thread overview]
Message-ID: <49551F6D.8010508@redhat.com> (raw)
In-Reply-To: <49532D27.2070902@oracle.com>

Wenji Huang wrote:
> Hi,
>
> I got building error for latest stap tree(commit 
> 46a8c85fde5ba9bcf4fa55e8f435959af4d32fea).
>
> [wjhuang@EL5U2-64bits ~]$ cat /tmp/error
> certutil: self-signing a cert request is not supported.
> certutil:  unable to open "ssl/server/stap-server.cert" for reading 
> (-5950, 2).
> Cannot find certificate file ssl/server/stap-server.cert
This is disturbing. We need to be able to sign our own certificates for 
this purpose, otherwise we're going to need to find or set up a 
certificate authority chain for our certificates. Can you provide more 
info about your system and which version of nss-tools is on it. Also the 
version of certutil and signtool?
>
> And for EL4,
>     certutil: command not found.
> Seems no nss-tools rpm available. I tried yum or up2date, but
> couldn't find nss-tools or certuils.
Also disturbing. I had been led to believe that nss and nss-tools were 
ubiquitous.

>
> Can we have option to enable/disable it, like
> ./configure --disable-stap-sever
I'll disable to the automatic building of stamp-ssl for now.
>
> Regards,
> Wenji
>
Dave


  reply	other threads:[~2008-12-26 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 18:28 Wenji Huang
2008-12-27 14:27 ` Dave Brolley [this message]
2008-12-29  2:20   ` Dave Brolley
2008-12-29 18:42   ` Wenji Huang
2008-12-31 20:34     ` Dave Brolley

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=49551F6D.8010508@redhat.com \
    --to=brolley@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wenji.huang@oracle.com \
    /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).