Teknoloji Haberleri
Bu konudaki kullanıcılar: 1 misafir
16
Cevap 910
Tıklama 0
Öne Çıkarma
Cevap 910
Tıklama 0
Öne Çıkarma
1. sayfa
-
pardus program yükleme
|
UNİSTALL DOSYASINA YAZANLAR BUNLAR: Installation Instructions ************************* Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free Software Foundation, Inc. This file is free documentation; the Free Software Foundation gives unlimited permission to copy, distribute and modify it. Basic Installation ================== These are generic installation instructions. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, and a file `config.log' containing compiler output (useful mainly for debugging `configure'). It can also use an optional file (typically called `config.cache' and enabled with `--cache-file=config.cache' or simply `-C') that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.) If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If you are using the cache, and at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.ac' (or `configure.in') is used to create `configure' by a program called `autoconf'. You only need `configure.ac' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself. Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for. 2. Type `make' to compile the package. 3. Optionally, type `make check' to run any self-tests that come with the package. 4. Type `make install' to install the programs and any data files and documentation. 5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution. Compilers and Options ===================== Some systems require unusual options for compilation or linking that the `configure' script does not know about. Run `./configure --help' for details on some of the pertinent environment variables. You can give `configure' initial values for configuration parameters by setting variables in the command line or in the environment. Here is an example: ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix *Note Defining Variables::, for more details. Compiling For Multiple Architectures ==================================== You can compile the package for more than one kind of computer at the same time, by placing the object files for each architecture in their own directory. To do this, you must use a version of `make' that supports the `VPATH' variable, such as GNU `make'. `cd' to the directory where you want the object files and executables to go and run the `configure' script. `configure' automatically checks for the source code in the directory that `configure' is in and in `..'. If you have to use a `make' that does not support the `VPATH' variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use `make distclean' before reconfiguring for another architecture. Installation Names ================== By default, `make install' installs the package's commands under `/usr/local/bin', include files under `/usr/local/include', etc. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PREFIX'. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you pass the option `--exec-prefix=PREFIX' to `configure', the package uses PREFIX as the prefix for installing programs and libraries. Documentation and other data files still use the regular prefix. In addition, if you use an unusual directory layout you can give options like `--bindir=DIR' to specify different values for particular kinds of files. Run `configure --help' for a list of the directories you can set and what kinds of files go in them. If the package supports it, you can cause programs to be installed with an extra prefix or suffix on their names by giving `configure' the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. Optional Features ================= Some packages pay attention to `--enable-FEATURE' options to `configure', where FEATURE indicates an optional part of the package. They may also pay attention to `--with-PACKAGE' options, where PACKAGE is something like `gnu-as' or `x' (for the X Window System). The `README' should mention any `--enable-' and `--with-' options that the package recognizes. For packages that use the X Window System, `configure' can usually find the X include and library files automatically, but if it doesn't, you can use the `configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their locations. Specifying the System Type ========================== There may be some features `configure' cannot figure out automatically, but needs to determine by the type of machine the package will run on. Usually, assuming the package is built to be run on the _same_ architectures, `configure' can figure that out, but if it prints a message saying it cannot guess the machine type, give it the `--build=TYPE' option. TYPE can either be a short name for the system type, such as `sun4', or a canonical name which has the form: CPU-COMPANY-SYSTEM where SYSTEM can have one of these forms: OS KERNEL-OS See the file `config.sub' for the possible values of each field. If `config.sub' isn't included in this package, then this package doesn't need to know the machine type. If you are _building_ compiler tools for cross-compiling, you should use the option `--target=TYPE' to select the type of system they will produce code for. If you want to _use_ a cross compiler, that generates code for a platform different from the build platform, you should specify the "host" platform (i.e., that on which the generated programs will eventually be run) with `--host=TYPE'. Sharing Defaults ================ If you want to set default values for `configure' scripts to share, you can create a site shell script called `config.site' that gives default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script. Defining Variables ================== Variables not defined in a site shell script can be set in the environment passed to `configure'. However, some packages may run configure again during the build, and the customized values of these variables may be lost. In order to avoid this problem, you should set them in the `configure' command line, using `VAR=value'. For example: ./configure CC=/usr/local2/bin/gcc causes the specified `gcc' to be used as the C compiler (unless it is overridden in the site shell script). Here is a another example: /bin/bash ./configure CONFIG_SHELL=/bin/bash Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent configuration-related scripts to be executed by `/bin/bash'. `configure' Invocation ====================== `configure' recognizes the following options to control how it operates. `--help' `-h' Print a summary of the options to `configure', and exit. `--version' `-V' Print the version of Autoconf used to generate the `configure' script, and exit. `--cache-file=FILE' Enable the cache: use and save the results of the tests in FILE, traditionally `config.cache'. FILE defaults to `/dev/null' to disable caching. `--config-cache' `-C' Alias for `--cache-file=config.cache'. `--quiet' `--silent' `-q' Do not print messages saying which checks are being made. To suppress all normal output, redirect it to `/dev/null' (any error messages will still be shown). `--srcdir=DIR' Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically. `configure' also accepts some other, not widely useful, options. Run `configure --help' for more details. |
|
arkadaşlar baya bi uğraştım biraz ilerledim süper kullanıcı conso lunu açtım şifremi girdim masa üstünden yüklicem programı mause la tutp console ekranına getirip bıraktım hemen secenek cıkıyo cd rd vb.. diye bende cd yaptım sonra ./configure yazdım baya bi taradı yes no şu şekilde ve sonunda hata veriyo nette sistem kütüphanesinde eksikliklerden kaynaklanıyodiyo bendw güncellemeler tam tarama sonucu: pardus ~ # cd '/home/siya6153/Desktop/audacious-1.5.0' pardus audacious-1.5.0 # ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether NLS is requested... yes checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/gmsgfmt checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for ranlib... ranlib checking for strerror in -lcposix... no checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for off_t... yes checking for size_t... yes checking for working alloca.h... yes checking for alloca... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking whether we are using the GNU C Library 2.1 or newer... yes checking whether integer division by zero raises SIGFPE... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unsigned long long... yes checking for inttypes.h... yes checking whether the inttypes.h PRIxNN macros are broken... no checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for shared library run path origin... done checking argz.h usability... yes checking argz.h presence... yes checking for argz.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking nl_types.h usability... yes checking nl_types.h presence... yes checking for nl_types.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking for feof_unlocked... yes checking for fgets_unlocked... yes checking for getc_unlocked... yes checking for getcwd... yes checking for getegid... yes checking for geteuid... yes checking for getgid... yes checking for getuid... yes checking for mempcpy... yes checking for munmap... yes checking for putenv... yes checking for setenv... yes checking for setlocale... yes checking for stpcpy... yes checking for strcasecmp... yes checking for strdup... yes checking for strtoul... yes checking for tsearch... yes checking for __argz_count... yes checking for __argz_stringify... yes checking for __argz_next... yes checking for __fsetlocking... yes checking for iconv... yes checking for iconv declaration... extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); checking for nl_langinfo and CODESET... yes checking for LC_MESSAGES... yes checking for bison... bison checking version of bison... 2.1, ok checking whether NLS is requested... yes checking whether included gettext is requested... no checking for GNU gettext in libc... yes checking whether to use NLS... yes checking where the gettext function comes from... libc checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for strerror in -lcposix... (cached) no checking whether byte ordering is bigendian... no checking for style of include used by make... GNU checking dependency style of gcc... none checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for rm... /usr/bin/rm checking for mv... /usr/bin/mv checking for cp... /usr/bin/cp checking for ar... /usr/bin/ar checking for ranlib... /usr/bin/ranlib checking for audacious... no checking for pkg-config... /usr/bin/pkg-config checking for glib-2.0 >= 2.14.0 gthread-2.0... yes checking GLIB_CFLAGS... -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking GLIB_LIBS... -pthread -lgthread-2.0 -lrt -lglib-2.0 checking for gtk+-2.0 >= 2.10.0... yes checking GTK_CFLAGS... -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking GTK_LIBS... -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 checking for pango >= 1.8.0... yes checking PANGO_CFLAGS... -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include checking PANGO_LIBS... -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 checking for libmowgli >= 0.4.0... no configure: error: Cannot find libmowgli, tryhttp://www.atheme.org/projects/mowgli.shtml pardus audacious-1.5.0 # |
Bu mesaja 1 cevap geldi.
|
orada açıklama yapmış zaten. mowgli kütüphanesi yok.http://www.atheme.org/projects/mowgli.shtml adresinden indirip kurabilirsin demiş. birde foruma output yapıştırırken tümünü değilde error satırını yapıştırırsan okunabilirlik açısından daha iyi olur. |
Bu mesaja 1 cevap geldi.
| ricco uyardığın için sağol dedin gibi o dosyayı indirdim masa üstüne sonra aynı şekilde maus la çekip console getirdim ./configure yazdım taradı hata vermedi sonra make yazdım oda hata vermedi sonra make uninstall yazdım ve kurdum sonra ne yapıcamı bilmiyorum yani bu değişiklik otomatik kaydediliyo heralde bende reboot yapıp tekrar başlattım pc yi sonra programımı kurmak gine aynı consola çekip bıraktıp cd dedim ./configure ama gine aynı hata halbuki hata vermeden eksik dosyayı yükledim yardım |
Bu mesaja 1 cevap geldi.
| "make uninstall" değil "make install" demen gerekiyor. restarta gerek yok. eğer libmowgli kütüphanesi hatasız olarak install edildiyse audacious klasörüne geçip tekrar ./configure demen gerekiyor. yannız audacious sitesinde download sayfasına dikkat ettiysen başka gerekli kütüphanelerde var. yani configure sırasında başka hatalar gelebilir. gereken tüm kütüphaneleri kurman gerekecek. ama bu işin sonunda linuxa program kurmayıda bayaa öğreneceksin sanırım :) |
Bu mesaja 1 cevap geldi.
| yok dostum yok dediği dosyayı hatasız kuruyorum sonra tekran mp3 programını kurmaya çalışıyorum kurulduğu halde libmowgli diye hata veriyo halbuki hatasız kurdum |
Bu mesaja 1 cevap geldi.
checking for libmowgli >= 0.4.0... no configure: error: Cannot find libmowgli, tryhttp://www.atheme.org/projects/mowgli.shtml hata mesajından kurdugunuzu soyledıgınız dosyanın kurulumda bulunamadıgı gozukuyor. |
Bu mesaja 1 cevap geldi.
|
ama "make uninstall" demiştin. bu komutla yüklemez, kurulu programı silersin. libmowgli kurarken sırayla ./configure make make install dediğine eminmisin |
Bu mesaja 2 cevap geldi.
|
./configure make make install bu komutlarla başarılı bi şekilde yüklüyorum ama hala daha arıyo başka bişe lazım ama ne |
Ben şuanda bir windows programı olan Quintessential Player wine ile kullanıyom süper çalışıyor hemde hertürlü skinlerini bile kullanabiliyorum hemde türkçe  |
Bu mesaja 1 cevap geldi.
|
olmuyor diyince şuan slackwarede denedim ve hiçbir problem yaşamadan kuruldu. pardus kullanıcısı değilim pardusta farklı klasörlerde olabilir ama büyük ihtimalle aynıdır. /etc/ld.so.conf dosyası içesininde /usr/local/lib satırının olduğunu kontrol edip, eğer yoksa ekledikten sonra sudo ldconfig komutunu çalıştırıp daha sonra yeniden programı kurmayı deniyebilirmisin? |
Bu mesaja 2 cevap geldi.
| şu wine olayını biraz açarmısınzı nerden indiriyorum nasıl kuruyorum wine onlada denerim olmazsa |
var dostum kontrol ettim yardım edin valla daraldım yaa |
Bu mesaja 1 cevap geldi.
|
İstediğin program katkı deposunda var. http://www.ozgurlukicin.com/nasil/katki-contrib-deposu-ekleme/ Bu adrestekileri uygula.Daha sonra paket yöneticisi ile rahtlıkla kurabilirsin. |
Bu mesaja 1 cevap geldi.
arkadaşım senin dedin gibi verdiğin sitedeki linki koydum benim deop linklerim şunlar depo adı:ds deop adresi:http://paketler.pardus.org.tr/contrib-2007/pisi-index.xml.bz2 deopo adı:pardus-2007.3 depo adresi:http://paketler.pardus.org.tr/pardus-2007.3/pisi-index.xml.bz2 o linktekini ekledim güncelleniyo dedi bittimi arama yerine wine yazdım çıkmadı anlamadım sölenenleri yapıyorum ama yok   birde varsa daha depo linkleri verirseniz sevinirim bide bi sorum daha olucak şimdi ben program indirirken direk googla linux programları yazıp bulup indiriyorum yani pardus ta sonuçta linux öle değilmi yani yanlış yapmıyotum heralde |
< Bu mesaj bu kişi tarafından değiştirildi -Pardus- -- 26 Mart 2008; 17:56:14 >
Bu mesaja 1 cevap geldi.
1. sayfa
DH Mobil uygulaması ile devam edin.
Mobil tarayıcınız ile mümkün olanların yanı sıra, birçok yeni ve faydalı özelliğe erişin.
Gizle ve güncelleme çıkana kadar tekrar gösterme.
DH forumlarında vakit geçirmekten keyif alıyor gibisin ancak giriş yapmadığını görüyoruz.
Üye Ol Şimdi DeğilÜye olduğunda özel mesaj gönderebilir, beğendiğin konuları favorilerine ekleyip takibe alabilir ve daha önce gezdiğin konulara hızlıca erişebilirsin.
< Bu mesaj bu kişi tarafından değiştirildi -Pardus- -- 25 Mart 2008; 16:39:18 >