Написаны обычные вещи, она мне уже снится.
INSTALLING Qt/X11 Version 4.5.0.
1. If you have the commercial edition of Qt, install your license
file as $HOME/.qt-license.
For the open source version you do not need a license file.
2. Unpack the archive if you have not done so already:
cd /tmp
gunzip %DISTNAME%.tar.gz # uncompress the archive
tar xvf %DISTNAME%.tar # unpack it
This creates the directory /tmp/%DISTNAME% containing the files
from the archive. We only support the GNU version of the tar
archiving utility. Note that on some systems it is called gtar.
3. Building
To configure the Qt library for your machine type, run the
./configure script in the package directory.
By default, Qt is configured for installation in the
/usr/local/Trolltech/Qt-4.5.0 directory, but this can be
changed by using the -prefix option. Alternatively, the
-prefix-install option can be used to specify a «local»
installation within the source directory.
cd /tmp/%DISTNAME%
./configure
Type «./configure -help» to get a list of all available options.
To create the library and compile all the demos, examples, tools,
and tutorials, type:
make
If you did not configure Qt using the -prefix-install option,
you need to install the library, demos, examples, tools, and
tutorials in the appropriate place. To do this, type:
su -c «make install»
and enter the root password.
Note that on some systems the make utility is named differently,
e.g. gmake. The configure script tells you which make utility to
use.
If you need to reconfigure and rebuild Qt from the same location,
ensure that all traces of the previous configuration are removed
by entering the build directory and typing
make confclean
before running the configure script again.
4. Environment variables
In order to use Qt, some environment variables needs to be
extended.
PATH — to locate qmake, moc and other Qt tools
This is done like this:
In .profile (if your shell is bash, ksh, zsh or sh), add the
following lines:
PATH=/usr/local/Trolltech/Qt-4.5.0/bin:$PATH
export PATH
In .login (in case your shell is csh or tcsh), add the following line:
setenv PATH /usr/local/Trolltech/Qt-4.5.0/bin:$PATH
If you use a different shell, please modify your environment
variables accordingly.
For compilers that do not support rpath you must also extended the
LD_LIBRARY_PATH environment variable to include
/usr/local/Trolltech/Qt-4.5.0/lib. On Linux with GCC this step
is not needed.
5. That’s all. Qt is now installed.
If you are new to Qt, we suggest that you take a look at the demos
and examples to see Qt in action. Run the Qt Examples and Demos
either by typing ‘qtdemo’ on the command line or through the
desktop’s Start menu.
You might also want to try the following links:
http://doc.trolltech.com/4.5.0/how-to-learn-qt.html
http://doc.trolltech.com/4.5.0/tutorial.html
http://qtsoftware.com/developer
We hope you will enjoy using Qt. Good luck!
sania77
(09.06.17 14:45:24 MSK)
- Показать ответ
- Ссылка
- Печать
Страницы: [1] 2 3 4 Все Вниз
Тема: Установка приложений их исходных кодов (Прочитано 12786 раз)
0 Пользователей и 1 Гость просматривают эту тему.
Yujeen33
Доброго времени суток. Столкнулся с такой проблемой. Пытаюсь собрать приложение из исходников. Выполнил:
1. sudo apt-get install checkinstall
2. Доставил automake, autoconf
3. Перехожу в каталог с исходниками
4. Выполняю команду ./configure — результат: yujeen@HOLDER:~/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose$ ./configure . bash: ./configure: Нет такого файла или каталога
Вопрос — в чем ошибка?
ТС не появлялся на Форуме более трех месяцев по состоянию на 05/12/2019 (последняя явка: 26/08/2019). Модератором раздела принято решение закрыть тему.
—zg_nico
« Последнее редактирование: 05 Декабря 2019, 07:36:36 от zg_nico »
| toZen |
Ошибка в том, что установка происходит в данном случае иначе. Вы смотрели содержимое директории с исходниками? Файл README или INSTALL имеется в наличии? Там всё расписано, как ставить, в какую директорию обращаться.
F12
Yujeen33
Я это все читал. Команда make не выполняется, т.к. кое-что отсутствует. http://ubuntu.ucoz.net/publ/howto/21-1-0-19 рекомендует сначала сконфигурировать и доставить зависимости, но проблема в том, что получается то что нет configure файла. Как его поставить?
symon2014
Yujeen33, В ссылке , представленной F12 , описано создание файла configure.
Pit Sullivan
Если configure нет вместе с исходным кодом программы, то, вероятно, он и не требуется. Читайте файлы README и INSTALL для каждой отдельной программы, как уже было справедливо отмечено, а не вот такие статьи с общими рекомендациями, которые только сбивают Вас с толку. Приведите пожалуйста вывод команды make.
Yujeen33
yujeen@HOLDER:~/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose$ make
make -C po
make[1]: Вход в каталог `/home/yujeen/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose/po’
msgfmt -c -v -o de.mo de.po
de.po:7: предупреждение: в заголовке отсутствует поле «Language»
17 переведённых сообщений.
msgfmt -c -v -o ru.mo ru.po
ru.po:2: предупреждение: в заголовке отсутствует поле «Language»
17 переведённых сообщений.
msgfmt -c -v -o it.mo it.po
it.po:9: предупреждение: в заголовке отсутствует поле «Language»
17 переведённых сообщений.
msgfmt -c -v -o pl.mo pl.po
pl.po:2: предупреждение: в заголовке отсутствует поле «Language»
17 переведённых сообщений.
make[1]: Выход из каталога `/home/yujeen/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose/po’
make -C src
make[1]: gimptool-2.0: Команда не найдена
make[1]: Вход в каталог `/home/yujeen/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose/src’
Пользователь решил продолжить мысль 31 Мая 2015, 12:16:42:
А вот вывод при создании конфигурационного файла
yujeen@HOLDER:~/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose$ aclocal
aclocal: error: ‘configure.ac’ is required
yujeen@HOLDER:~/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose$ autoheader
autoheader: ‘configure.ac’ or ‘configure.in’ is required
yujeen@HOLDER:~/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose$ automake —gnu —add-missing —copy —foreign
automake: error: ‘configure.ac’ is required
yujeen@HOLDER:~/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose$ autoconf -f -Wall
autoconf: error: no input file
yujeen@HOLDER:~/Загрузки/gimp-plugins-ambulance-parmuss-wavelet-decompose$
« Последнее редактирование: 31 Мая 2015, 12:16:42 от Yujeen33 »
Pit Sullivan
Yujeen33, откройте окно терминала и введите следующее:
sudo apt-get install libgimp2.0-devДождитесь завершения установки, затем перейдите в директорию, в которой находится плагин, и введите следующую последовательность команд:
makeP.S. В директории проекта есть файлы README и INSTALL. Признайтесь, ведь не читали?
sudo make install
« Последнее редактирование: 01 Июня 2015, 08:25:30 от Pit Sullivan »
Yujeen33
Все читал, но вот что получилось
Похоже без конфигуратора не пойдет, а его по прежнему нет.
Листинги и содержимое текстовых файлов следует добавлять в сообщение с помощью тега
—HP
« Последнее редактирование: 01 Июня 2015, 20:06:47 от Haron Prime »
Pit Sullivan
Yujeen33, wavelet-denoise-0.3.1 — это уже другой проект, Вам не кажется? Что с wavelet-decompose?
« Последнее редактирование: 01 Июня 2015, 10:26:22 от Pit Sullivan »
Yujeen33
Они его поменяли. Этот более новый. Принцип то не меняется. Процедура та же. это в файле install написано. Что дальше? Я раньше не собирал из исходников, поэтому и вопросы. Все посты рекомендуют сначала скомпилировать пакет, а этого не происходит. Почему -вот вопрос. Я прогуглил уже много страниц. Этот вариант с компиляцией все считают правильным.
Pit Sullivan
Ну так Вы сами сперва пытались собрать один проект и попросили помощи. Я стараюсь Вам помочь, но ничего не выходит, так как, оказывается, Вы пытаетесь собрать уже совсем другой проект. И кто эти загадочные «они»? Поделитесь пожалуйста ссылкой на архивы с проектами.
…а этого не происходит. Почему -вот вопрос.
Потому что не хватает библиотеки libm.so.6, вот почему. Это ошибка линкования. Придётся вручную отредактировать Makefile.
Я раньше не собирал из исходников
Не беда, я помогу. Но для начала давайте как-нибудь синхронизируем наши действия, хорошо?
F12
Yujeen33,
а в чем проблема, разве вот эта инструкция не работает?..
вот
| toZen |
Yujeen33, боевик какой-то. Скиньте линк на архив, попробую у себя.
- Печать
Страницы: [1] 2 3 4 Все Вверх
glib will fail to build with the updated CFLAGS from pacman 5.2.2-3 but that is unrelated to the warnings from autotools:
autoreconf: warning: autoconf input should be named 'configure.ac', not 'configure.in'
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:63: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:9482: AM_INIT_AUTOMAKE is expanded from...
configure.in:63: the top level
configure.in:66: warning: 'AM_CONFIG_HEADER': this macro is obsolete.
configure.in:66: You should use the 'AC_CONFIG_HEADERS' macro instead.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:9816: AM_CONFIG_HEADER is expanded from...
configure.in:66: the top level
configure.in:75: warning: The macro `AM_PROG_LIBTOOL' is obsolete.
configure.in:75: You should run autoupdate.
aclocal.m4:122: AM_PROG_LIBTOOL is expanded from...
configure.in:75: the top level
configure.in:157: warning: 'AM_PROG_CC_STDC': this macro is obsolete.
configure.in:157: You should simply use the 'AC_PROG_CC' macro instead.
configure.in:157: Also, your code should no longer depend upon 'am_cv_prog_cc_stdc',
configure.in:157: but upon 'ac_cv_prog_cc_stdc'.
./lib/autoconf/general.m4:2434: AC_DIAGNOSE is expanded from...
aclocal.m4:9822: AM_PROG_CC_STDC is expanded from...
configure.in:157: the top level
configure.in:190: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:190: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
configure.in:190: the top level
configure.in:185: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:185: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
configure.in:185: the top level
configure.in:207: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:207: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
configure.in:207: the top level
configure.in:203: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:203: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
configure.in:203: the top level
configure.in:214: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.in:214: You should run autoupdate.
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.in:214: the top level
configure.in:236: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:236: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:236: the top level
configure.in:251: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:251: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:251: the top level
configure.in:266: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:266: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:266: the top level
configure.in:301: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:301: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.in:301: the top level
configure.in:313: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:313: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.in:313: the top level
configure.in:324: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:324: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
configure.in:324: the top level
configure.in:334: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:334: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
configure.in:334: the top level
configure.in:339: warning: The macro `AC_HEADER_EGREP' is obsolete.
configure.in:339: You should run autoupdate.
./lib/autoconf/oldnames.m4:37: AC_HEADER_EGREP is expanded from...
configure.in:339: the top level
configure.in:357: warning: The macro `AC_TRY_CPP' is obsolete.
configure.in:357: You should run autoupdate.
./lib/autoconf/general.m4:2762: AC_TRY_CPP is expanded from...
configure.in:357: the top level
configure.in:366: warning: The macro `AC_TRY_CPP' is obsolete.
configure.in:366: You should run autoupdate.
./lib/autoconf/general.m4:2762: AC_TRY_CPP is expanded from...
configure.in:366: the top level
configure.in:378: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:378: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.in:378: the top level
configure.in:401: warning: AC_CACHE_VAL(glib_cv_sane_realloc, ...): suspicious presence of an AC_DEFINE in the second argument, where no actions should be taken
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:401: the top level
configure.in:401: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:401: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:401: the top level
configure.in:422: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:422: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:422: the top level
configure.in:444: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:444: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:444: the top level
configure.in:466: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:466: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:466: the top level
configure.in:529: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:529: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.in:529: the top level
configure.in:529: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:529: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2894: _AC_LINK_IFELSE is expanded from...
./lib/autoconf/general.m4:2911: AC_LINK_IFELSE is expanded from...
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.in:529: the top level
configure.in:559: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:559: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
configure.in:559: the top level
configure.in:590: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:590: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:590: the top level
configure.in:835: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:835: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
configure.in:835: the top level
configure.in:857: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:857: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
configure.in:857: the top level
configure.in:870: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:870: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
configure.in:870: the top level
configure.in:877: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:877: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
configure.in:877: the top level
configure.in:886: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:886: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
configure.in:886: the top level
configure.in:927: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:927: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
acglib.m4:29: GLIB_SIZEOF is expanded from...
configure.in:927: the top level
configure.in:931: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:931: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
acglib.m4:54: GLIB_BYTE_CONTENTS is expanded from...
configure.in:931: the top level
configure.in:943: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:943: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
acglib.m4:84: GLIB_SYSDEFS is expanded from...
configure.in:943: the top level
configure.in:955: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete.
configure.in:955: You should run autoupdate.
./lib/autoconf/status.m4:1025: AC_OUTPUT_COMMANDS is expanded from...
configure.in:955: the top level
configure.in:1352: warning: AC_OUTPUT should be used without arguments.
configure.in:1352: You should run autoupdate.
autoheader: warning: autoconf input should be named 'configure.ac', not 'configure.in'
autoheader: warning: WARNING: Using auxiliary files such as 'acconfig.h', 'config.h.bot'
autoheader: WARNING: and 'config.h.top', to define templates for 'config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of 'AC_DEFINE_UNQUOTED' and
autoheader: WARNING: 'AC_DEFINE' allows one to define a template without
autoheader: WARNING: 'acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function 'main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:63: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
configure.in:63: https://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.in:75: installing './compile'
configure.in:63: installing './missing'
Makefile.am:73: warning: BUILT_SOURCES multiply defined in condition TRUE ...
Makefile.am:11: ... 'BUILT_SOURCES' previously defined here
Makefile.am:14: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Makefile.am: installing './depcomp'
gmodule/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
gthread/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
tests/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
parallel-tests: installing './test-driver'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for x86_64-unknown-linux-gnu-strip... no
checking for strip... strip
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking whether make supports the include directive... yes (GNU style)
checking for x86_64-unknown-linux-gnu-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... no
checking for x86_64-unknown-linux-gnu-dumpbin... no
checking for x86_64-unknown-linux-gnu-link... no
checking for dumpbin... no
checking for link... link -dump
checking the name lister (nm) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for x86_64-unknown-linux-gnu-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for x86_64-unknown-linux-gnu-dlltool... no
checking for dlltool... no
checking how to associate runtime and link libraries... printf %sn
checking for x86_64-unknown-linux-gnu-ar... no
checking for ar... ar
checking for archiver @FILE support... @
checking for x86_64-unknown-linux-gnu-strip... strip
checking for x86_64-unknown-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking command to parse nm output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for x86_64-unknown-linux-gnu-mt... no
checking for mt... no
checking if : is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether to enable memory checking... no
checking whether to enable memory profiling... no
checking for x86_64-unknown-linux-gnu-gcc... gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for x86_64-unknown-linux-gnu-gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for extra flags to get ANSI library prototypes... ./configure: line 14773: ac_fn_c_try_run: command not found
configure: WARNING: No ANSI prototypes found in library. (-std1 didn't work.)
checking for extra flags for POSIX compliance... none needed
checking for egrep... (cached) /usr/bin/grep -E
checking for vprintf... yes
checking for atexit... yes
checking for on_exit... yes
checking size of char... 1
checking size of short... 2
checking size of long... 8
checking size of int... 4
checking size of void *... 8
checking size of long long... 8
checking for an ANSI C-conforming const... yes
checking for __inline... yes
checking for __inline__... yes
checking for inline... yes
checking whether byte ordering is bigendian... no
checking for float.h... yes
checking for limits.h... yes
checking for pwd.h... yes
checking for sys/param.h... yes
checking for sys/poll.h... yes
checking for sys/select.h... yes
checking for sys/time.h... yes
checking for sys/times.h... yes
checking for unistd.h... (cached) yes
checking for values.h... yes
checking for lstat... yes
checking for strerror... yes
checking for strsignal... yes
checking for memmove... yes
checking for vsnprintf... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for poll... yes
checking for sys_errlist... no
checking for sys_siglist... no
checking for sys_siglist declaration... no
checking for fd_set... yes, found in sys/types.h
checking for wchar.h... no
checking for wctype.h... no
checking for iswalnum... yes
checking if iswalnum() and friends are properly defined... yes
checking whether realloc (NULL,) will work... yes
checking for an implementation of va_copy()... yes
checking for an implementation of __va_copy()... yes
checking whether va_lists can be copied by value... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking for dlsym in -ldl... yes
checking for RTLD_GLOBAL brokenness... no
checking for preceeding underscore in symbols... no
checking for dlerror... yes
checking for pthread.h... yes
checking for thread implementation... posix
checking for pthread_attr_init in -lpthread... yes
checking necessary linker options... -lpthread
configure: WARNING: I can't find the MACRO, that enables thread safety on your
platform (normally it's _REENTRANT). I'll not use any flag on
compilation now, but then your programs might not work.
Please provide information on how it is done on your system.
checking necessary compiler options...
checking for localtime_r... yes
checking for rand_r... yes
checking for getpwuid_r... yes
checking whether getpwuid_r is posix like... yes
checking whether pthread_getspecific is posix like... yes
checking whether pthread_mutex_trylock is posix like... yes
checking whether pthread_cond_timedwait is posix like... yes
checking size of pthread_mutex_t... 40
checking byte contents of pthread_mutex_t... 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
checking system definitions for POLLIN POLLOUT POLLPRI POLLERR POLLHUP POLLNVAL... done
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating glib.spec
config.status: creating Makefile
config.status: creating glib-config
config.status: creating gmodule/gmoduleconf.h
config.status: creating gmodule/Makefile
config.status: creating gthread/Makefile
config.status: creating docs/Makefile
config.status: creating docs/glib-config.1
config.status: creating tests/Makefile
config.status: creating glib.pc
config.status: creating gmodule.pc
config.status: creating gthread.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
creating glibconfig.h
config.status: executing default commands
CONFIG_FILES= CONFIG_HEADERS= CONFIG_OTHER=glibconfig.h ./config.status
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
creating glibconfig.h
glibconfig.h is unchanged
config.status: executing default commands
echo timestamp > stamp-gc-h
make all-recursive
make[1]: Entering directory '/build/glib/src/glib-1.2.10'
Making all in .
make[2]: Entering directory '/build/glib/src/glib-1.2.10'
gcc -DHAVE_CONFIG_H -I. -DG_LOG_DOMAIN=g_log_domain_glib -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2,-D_GLIBCXX_ASSERTIONS -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wall -MT testglib.o -MD -MP -MF .deps/testglib.Tpo -c -o testglib.o testglib.c
testglib.c: In function ‘main’:
testglib.c:904:3: error: format not a string literal and no format arguments [-Werror=format-security]
904 | g_print (string);
| ^~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [Makefile:727: testglib.o] Error 1
make[2]: Leaving directory '/build/glib/src/glib-1.2.10'
make[1]: *** [Makefile:847: all-recursive] Error 1
make[1]: Leaving directory '/build/glib/src/glib-1.2.10'
make: *** [Makefile:528: all] Error 2
[1m[31m==> ERROR:(B[m[1m A failure occurred in build().(B[m
[1m Aborting...(B[mI’ve trying to create install package for hello world sample C program.
I’ve done following staps.
autoscan
mv configure.scan configure.ac
edit configure.ac to add some macros.
aclocal
create Makefile.am within
bin_PROGRAMS = hello
hello_SOURCES = hello.c
Finally I did automake .
Then I got messages bellow. .
configure.ac:12: error: required file './compile' not found
configure.ac:12: 'automake --add-missing' can install 'compile'
configure.ac:6: error: required file './missing' not found
configure.ac:6: 'automake --add-missing' can install 'missing'
Makefile.am: error: required file './INSTALL' not found
Makefile.am: 'automake --add-missing' can install 'INSTALL'
Makefile.am: error: required file './NEWS' not found
Makefile.am: error: required file './README' not found
Makefile.am: error: required file './AUTHORS' not found
Makefile.am: error: required file './ChangeLog' not found
Makefile.am: error: required file './COPYING' not found
Makefile.am: 'automake --add-missing' can install 'COPYING'
Makefile.am: error: required file './depcomp' not found
Makefile.am: 'automake --add-missing' can install 'depcomp'
There aren’t any strings including compile, missing ,NEW, README or the massage said being required in Makefile.am an configure.ac files.
What should I do?
Those are information about version of some products.
CentOS release 6.4
autocomf-2.69
automake-1.14
m4-1.4
Hello, both using automake or autoconf, here the error:
automake: warning: autoconf input should be named ‘configure.ac’, not ‘configure.in’
automake: warning: ‘configure.ac’ and ‘configure.in’ both present.
automake: proceeding with ‘configure.ac’
configure.ac: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal)
configure.ac:32: error: required file ‘./config.guess’ not found
configure.ac:32: ‘automake —add-missing’ can install ‘config.guess’
configure.ac:32: error: required file ‘./config.sub’ not found
configure.ac:32: ‘automake —add-missing’ can install ‘config.sub’
Docs/makefile.am:5: error: FINK does not appear in AM_CONDITIONAL
Docs/makefile.am:17: error: FINK does not appear in AM_CONDITIONAL
Source/makefile.am: error: required file ‘./depcomp’ not found
Source/makefile.am: ‘automake —add-missing’ can install ‘depcomp’
/usr/share/automake-1.14/am/depend2.am: error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.14/am/depend2.am: The usual way to define ‘am__fastdepCC’ is to add ‘AC_PROG_CC’
/usr/share/automake-1.14/am/depend2.am: to ‘configure.ac’ and run ‘aclocal’ and ‘autoconf’ again
/usr/share/automake-1.14/am/depend2.am: error: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.14/am/depend2.am: The usual way to define ‘AMDEP’ is to add one of the compiler tests
/usr/share/automake-1.14/am/depend2.am: AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/share/automake-1.14/am/depend2.am: AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.14/am/depend2.am: to ‘configure.ac’ and run ‘aclocal’ and ‘autoconf’ again
automake: warning: autoconf input should be named ‘configure.ac’, not ‘configure.in’
automake: warning: ‘configure.ac’ and ‘configure.in’ both present.
automake: proceeding with ‘configure.ac’
makefile.am:25: error: FINK does not appear in AM_CONDITIONAL
makefile.am:44: error: FINK does not appear in AM_CONDITIONAL
fapchat@fapchat-Lenovo-G570:~/Загрузки$ sudo apt-get install php-dev autoconf
[sudo] пароль для fapchat:
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Уже установлен пакет autoconf самой новой версии (2.69-11).
Уже установлен пакет php-dev самой новой версии (2:7.4+75+ubuntu18.04.1+deb.sury.org+1).
Обновлено 0 пакетов, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 1 пакетов не обновлено.
fapchat@fapchat-Lenovo-G570:~/Загрузки$ automake
automake: error: ‘configure.ac’ is required
P.S. Пакеты установлены не были, просто терминал закрыл после установки, потом чисто для форума снова ввёл команды
На форумах конечно есть вопросы по поводу ошибки
automake: error: ‘configure.ac’ is required
но не в этом случае. Так что же делать?
-
Вопрос заданболее двух лет назад
-
62 просмотра
sudo apt-get install php-dev autoconf automake — это одна строка, не две.
> Так что же делать?
установить automake:
sudo apt-get install automake
Пригласить эксперта
-
Показать ещё
Загружается…
09 февр. 2023, в 09:53
10 руб./за проект
09 февр. 2023, в 09:37
2000 руб./за проект
09 февр. 2023, в 09:28
5000 руб./за проект
Минуточку внимания
не могу скомпилить (куда-то делся configure)
Модератор: Bizdelnick
-
toboe
- Сообщения: 79
- ОС: Fedora 10
не могу скомпилить
Хочу установить из сорца. Мои действия:
1. tar xvzf cedega_6.1.i386.p2p.tgz
2.
[root@home cedega_6.1]# configure
-bash: configure: команда не найдена
3. Почитал вот то:
Если отсутствует configure, собираем его командами bootstrap или autogen.sh. Если нет и таких скриптов, то пробуем
aclocal
autoheader
automake –gnu –add-missing –copy –foreign
autoconf -f -Wall
4. Проверяем:
[root@home tmp]# aclocal
aclocal: `configure.ac’ or `configure.in’ is required
[root@home tmp]# automake —gnu —add-missing —copy —foreign
automake: `configure.ac’ or `configure.in’ is required
[root@home tmp]# autoheader
autoheader: `configure.ac’ or `configure.in’ is required
Кто-нибудь объясните — что это и как такое возможно? О_о Стоит Федора 10
MSI Mega BOOK M520b, Intel Pentium M 740 1.73 GHz, VGA compatible controller: Intel Corporation Mobile 915GM, 1.0 Gb ОЗУ, 80Gb Hdd
-
nesk
- Сообщения: 2268
- Статус: Линукссаксовец
- ОС: MS Windows XP Home SP3
- Контактная информация:
Re: не могу скомпилить
Сообщение
nesk » 09.03.2009 21:45
toboe писал(а): ↑
09.03.2009 21:41
2.
[root@home cedega_6.1]# configure
-bash: configure: команда не найдена
если бы там даже и был configure, то запускать его следовало так:
[root@home cedega_6.1]# ./configure
И можно даже не от рута.
Но я не думаю, что cedega распространяется в виде исходников.
советую обратить внимание на файлы README и INSTALL в каталоге cedega_6.1 или инструкцию на сейчас cedega
Внимание: У меня под рукой нет машины с Linux. Я не использую эту ОС. Ответы я даю либо по памяти, либо мне помогает гугл. Тщательно читайте маны по тем командам и конфигурационным файлам, которые я упоминаю.
0xDEFEC8ED
-
toboe
- Сообщения: 79
- ОС: Fedora 10
Re: не могу скомпилить
Сообщение
toboe » 09.03.2009 21:58
Может я ошибаюсь конечно. Первый раз с этим сталкваюсь…
Я скачал файл cedega-engine_6.1.cpkg в котором был cedega_6.1.i386.p2p.tgz. я так и подумал что это сорц 
[root@home cedega_6.1]# ./configure
Такая же реакция
советую обратить внимание на файлы README и INSTALL в каталоге cedega_6.1
Отсутсвуют
Все, разобрался. Темку можно удалить чтобы не позориться 
MSI Mega BOOK M520b, Intel Pentium M 740 1.73 GHz, VGA compatible controller: Intel Corporation Mobile 915GM, 1.0 Gb ОЗУ, 80Gb Hdd
-
blackst0ne
- Сообщения: 528
- Статус: ツ
- ОС: Ubuntu 9.04
Re: не могу скомпилить
Сообщение
blackst0ne » 10.03.2009 13:34
Вы бы написали как проблему решили свою для будущих поколений.
И добавьте в заголовке своей темы в самом начале конструкцию [Решено] , чтобы люди не тратили свое время на прочтение темы, которая уже неактуальна.
Спасибо за понимание.
Администрация! Пожалуйста, добавьте птичку «решено», а также соответствующую кнопку на ajax’е в теме (подробнее здесь).
-
Hi, I heard somewhere that when you install a .tar.bz2 file you should use the following code:
mkdir <obj>
cd <obj>
../configure —enable-debug
make
make installBut when I run «../configure —enable-debug» it doesn’t reconise it. But I’ve searched around a bit and found out that I need to type:
aclocal
automake
autoconfBut when I run that, it says «‘configure.ac’ or ‘configure.in’ is required».
How can I get those?
-
Re: ./configure
Try this
sudo apt-get install automake autoconf autotools build-essential
Also you just need to untar the the tar.bz2
Enter its folder via terminal
then follow the commands./configure —enable-debug
make
make install
-
Re: ./configure
Thanks, but you say that you «just need to untar», that’s exactly what I’m doing. My problem is, that when I type «./configure» it doesn’t understand it.
-
Re: ./configure
Thanks, but you say that you «just need to untar», that’s exactly what I’m doing. My problem is, that when I type «./configure» it doesn’t understand it.
-
Re: ./configure
are you untarring it first?
example:
tar -xvf myfile.tarseems like you need to cd into the untarred directory and ls to make sure the «configure» file is there…
I am confused on what you are having problems with
-
Re: ./configure
I wasn’t untarring it, I’ll go and try now. And newbies have some weird problems you know…
-
Re: ./configure
yeah I know aobut that…I am still a newb myself…I just had to learn the tar thing the hard way back on my mandrake 9 box
Good Luck
-
Re: ./configure
Oh, does it matter that it’s a .tar.bz2?
And I’ll try to explain my problem:
I have downloaded this program (if you want to know, opencity)
And in the install instructions it says this:mkdir obj
cd obj
../configure —enable-debug
make
make installSo my noobish knowledge and I go and run that code, everything goes just fine until we cross the line «../configure —enable-debug» when I type it the terminal produces the following output: «bash: ../configure: unknown file or directory»
But when I scroll down in the installing instructions it says:
In case you don’t have a configure script, the following
commands will creat one:aclocal
automake
autoconfSo I run those codes, but with each of the three it says: «aclocal/automake/autoconf: ‘configure.ac’ or ‘configure.in’ is required»
That’s my problem…
-
Re: ./configure
Ok, here’s what you do. You unpack the archive to somewhere easy to find, like your home directory or something. You can do this with Archive Manager for instance, probably just need to doubleclick the downloaded file for it to start.
Then, start a terminal and navigate *into* the created directory, probably named opencity something. You need to be inside this directory from the terminal. You could install nautilus-open-terminal to get a context menu entry for opening a terminal in a directory from nautilus (why oh why is this not default when it is so often needed).
Once inside that directory, when the prompt says opencity something in the path, you should be able to see the file configure there by typing «ls». Then, follow those instructions as they were typed. It should work just fine.
Another option is to try and see if you can find a prebuilt package for it. Even if it isn’t in the repositories, there’s sometimes .deb files available on the net. Type «sudo dpkg -i package-name.deb» to install such a package.
HTH
-
Re: ./configure
Thanks alot, that’ll do it.