From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Mr Dash Four <mr.dash.four@googlemail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] cannot build qemu with "--static" configure option
Date: Wed, 23 Nov 2011 23:53:53 +0400 [thread overview]
Message-ID: <201111232353.53878.jcmvbkbc@gmail.com> (raw)
In-Reply-To: <4ECD4E91.9060605@googlemail.com>
> > Do you have a static libgthread-2.0? (ie /usr/lib/libgthread-2.0.a or
> > equivalent).
> Nope, this is what I have:
>
> /usr/lib64/libgthread.so
> /usr/lib64/libgthread-2.0.so
> /usr/lib64/libgthread-1.2.so.0
> /usr/lib64/libgthread-1.2.so.0.0.10
>
> *but*, just downloaded the source rpm and looked at the .spec file. It contains the following few lines in the %build section:
>
> %configure --disable-static
> [...]
> ## Unpackaged files
> # info
> %{__rm} -rf %{buildroot}%{_infodir}
> # .la fies... die die die.
> %{__rm} -rf %{buildroot}%{_libdir}/lib*.la
> # despite use of --disable-static, delete static libs that get built anyway
> %{__rm} -rf %{buildroot}%{_libdir}/lib*.a
>
>
> So, somebody at Fedora doesn't like static (.a) files very much, it seems. I could easily correct this, enable static building and have these installed, I think.
There's glib2-static in Fedora:
$ rpm -ql glib2-static
/usr/lib64/libgio-2.0.a
/usr/lib64/libglib-2.0.a
/usr/lib64/libgmodule-2.0.a
/usr/lib64/libgobject-2.0.a
/usr/lib64/libgthread-2.0.a
Thanks.
-- Max
next prev parent reply other threads:[~2011-11-23 19:54 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
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 [this message]
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=201111232353.53878.jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=mr.dash.four@googlemail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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 NNTP newsgroup(s).