ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@altlinux.ru>
Subject: Re: [devel] Q: lt_cv_cc_static_works=no
Date: Tue, 23 Dec 2003 14:17:53 +0300
Message-ID: <20031223111753.GB906@basalt.office.altlinux.org> (raw)
In-Reply-To: <20031223064955.GF27085@inferno.immo>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

On Tue, Dec 23, 2003 at 09:49:55AM +0300, Alexey I. Froloff wrote:
> Обсуждали с taniwha на IRC последнюю проблему с libtool и
> статическими библиотеками.  Вот частичный лог:
> 
>  * raorn wonders, will it work with lt_cv_prog_cc_static_works=no....
> <raorn> hm... grep says, lt_cv_prog_cc_static_works=no will work...
> <taniwha> you really shouldn't be messing with that
> <taniwha> just configure with --disable-static
> <taniwha> for one thing, that only affects linking
> <raorn> taniwha: i'm afraid, this export will be included in
>         %configure rpm macro some day...
> <taniwha> if that happens, dump rpm
> <taniwha> or patch rpm to remove /any/ such export
> <raorn> as far as i can see
> <raorn> if it will cause any problems, rpm will be fixed ;-)
> <taniwha> still, why not do the sane thing and just use the
>           options to configure?
> 
> Вот действительно, зачем это нужно?

Это равносильно неустановке пакета glibc-devel-static.
Нужно это для того, чтобы в системе, где glibc-devel-static установлен,
buildreq не включал его в сборочные зависимости без необходимости.


-- 
ldv

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-23 11:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23  6:49 Alexey I. Froloff
2003-12-23 11:17 ` Dmitry V. Levin [this message]
2003-12-23 11:31   ` Alexey I. Froloff
2004-01-04 23:40     ` Alexey I. Froloff
2004-01-05  0:01       ` Dmitry V. Levin
2004-01-05 21:23         ` [devel] " Mikhail Zabaluev

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=20031223111753.GB906@basalt.office.altlinux.org \
    --to=ldv@altlinux.org \
    --cc=devel@altlinux.ru \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git