From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] cannot build qemu with "--static" configure option
Date: Wed, 23 Nov 2011 15:41:00 +0000 [thread overview]
Message-ID: <4ECD140C.7060102@googlemail.com> (raw)
In-Reply-To: <4ECD103C.60406@redhat.com>
>>> Perhaps you lack a static version of the library.
>> What do you mean by that? The *.la files? I wasn't aware that there are
>> any...
>
> I mean lib*.a files. They are needed if you specify static, by
> definition.
Hmm, this opens a huge Pandora's box for me - in my own distribution
(Fedora) the "nss" package (which I have installed) provides
/usr/lib64/libssl3.so, but not libssl3.a. "nss-devel" (which I also have
installed) provides all the relevant /include files (headers and the
like), but there is no libssl3.a there either! There is no package
called "nss-devel-static" distributed by Fedora and the only ".a" files
produced by compiling the nss source are libcrmf.a libnssb.a and
libnssckfw.a - no libssl3.a at all. So, where do I get this?
Also, assuming libssl3 is not the only one, ld will probably complain
that there are other ".a" files missing from various other packages
which are probably not present in my host machine. If that is the case,
this is an absolute nightmare to have to deal with! Where do I get these
files? Thanks for your input Paolo.
next prev parent reply other threads:[~2011-11-23 15:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 12:58 [Qemu-devel] cannot build qemu with "--static" configure option Mr Dash Four
2011-11-23 14:10 ` Paolo Bonzini
2011-11-23 14:15 ` Mr Dash Four
2011-11-23 15:24 ` Paolo Bonzini
2011-11-23 15:41 ` Mr Dash Four [this message]
2011-11-23 18:00 ` Paolo Bonzini
2011-11-23 18:28 ` Peter Maydell
2011-11-23 18:33 ` Mr Dash Four
2011-11-23 18:36 ` Peter Maydell
2011-11-23 18:42 ` Mr Dash Four
2011-11-23 18:47 ` Peter Maydell
2011-11-23 19:02 ` Mr Dash Four
2011-11-23 19:16 ` Peter Maydell
2011-11-23 19:22 ` Mr Dash Four
2011-11-23 19:33 ` Peter Maydell
2011-11-23 19:50 ` Mr Dash Four
2011-11-23 19:53 ` Max Filippov
2011-11-23 19:57 ` Mr Dash Four
2011-11-23 19:59 ` Peter Maydell
2011-11-23 20:08 ` Max Filippov
2011-11-23 20:18 ` Max Filippov
2011-11-23 20:28 ` Mr Dash Four
2011-11-23 23:02 ` Mr Dash Four
2011-11-23 23:15 ` Max Filippov
2011-11-23 23:22 ` Peter Maydell
2011-11-23 23:33 ` Mr Dash Four
2011-11-24 8:48 ` Max Filippov
2011-11-24 12:15 ` Mr Dash Four
2011-11-24 12:25 ` Paolo Bonzini
2011-11-24 12:45 ` Mr Dash Four
2011-11-23 20:27 ` Mr Dash Four
2011-11-23 20:39 ` Mr Dash Four
2011-11-23 20:51 ` Max Filippov
2011-11-23 21:00 ` Mr Dash Four
2011-11-23 21:40 ` Max Filippov
2011-11-23 22:12 ` Peter Maydell
2011-11-23 22:13 ` Peter Maydell
2011-11-23 20:13 ` Mr Dash Four
2011-11-24 12:26 ` Alon Levy
2011-11-24 12:57 ` Peter Maydell
2011-11-23 18:34 ` Mr Dash Four
2011-11-23 14:18 ` Peter Maydell
2011-11-23 14:39 ` Mr Dash Four
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=4ECD140C.7060102@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.