From: php-coder <php-coder@ngs.ru>
To: devel@lists.altlinux.org
Subject: [devel] checking for i686-alt-linux-g++... no
Date: Tue, 3 Jan 2006 17:21:30 +0600
Message-ID: <20060103112130.GA16064@mycomp.mydomain> (raw)
Здравствуйте!
Постоянно вижу при сборке программ в выводе configure-скрипта:
checking for i686-alt-linux-g++... no
checking for i686-alt-linux-c++... no
checking for i686-alt-linux-gpp... no
checking for i686-alt-linux-aCC... no
checking for i686-alt-linux-CC... no
checking for i686-alt-linux-cxx... no
checking for i686-alt-linux-cc++... no
checking for i686-alt-linux-cl... no
checking for i686-alt-linux-FCC... no
checking for i686-alt-linux-KCC... no
checking for i686-alt-linux-RCC... no
checking for i686-alt-linux-xlC_r... no
checking for i686-alt-linux-xlC... no
....
Зачем эти проверки? Можно ли их как-нибудь отключить ?
И еще не понянтны подобные только зачем-то фортрановский компилятор
ищет (а программа на С++):
...
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
...
Подскажите, что всё это значит?! :)
--
+ php-coder
+ php-coder[at]altlinux[dot]ru
next reply other threads:[~2006-01-03 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 11:21 php-coder [this message]
2006-01-03 13:43 ` Mikhail Zabaluev
2006-01-04 16:16 ` Dmitry V. Levin
2006-01-03 16:22 ` [devel] " Konstantin A. Lepikhov
2006-01-04 11:40 ` [devel] [JT] " Andrei Bulava
2006-01-04 11:50 ` [devel] " Konstantin A. Lepikhov
2006-01-04 12:07 ` Igor Zubkov
2006-01-04 14:15 ` Mikhail Zabaluev
2006-01-04 15:02 ` Konstantin A. Lepikhov
2006-01-04 23:16 ` 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=20060103112130.GA16064@mycomp.mydomain \
--to=php-coder@ngs.ru \
--cc=devel@lists.altlinux.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
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