BitTorrent-4.3.5-1-Python2.4.noarch.rpm
rpm -ivh BitTorrent-4.3.5-1-Python2.4.noarch.rpm以后怎么用运行，怎么用它来下载BT？？ 这个不好用，用java版的那个Azureus : Java BitTorrent Client
[url]http://azureus.sourceforge.net/[/url] azureus好东西呀
不过在我的ubuntu里老是崩溃
郁闷中
不用rpm
无法回复LZ的问题
我现在用的是bitstormlite
楼主只要查到这个rpm安装上来bin目录里有什么就可以了
rpm -ql 包名 | grep bin windows 下utorrent好用,不知道linux有没有 我下了ktorrent-2.1beta1.tar.gz
#tar zxvf ktorrent-2.1beta1.tar.gz
#cd ktorrent-2.1beta1
# ./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 for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for kde-config... /usr/bin/kde-config
checking where to install... /usr (as returned by kde-config)
checking for style of include used by make... GNU
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 ANSI C... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether g++ supports -Wmissing-format-attribute... yes
checking whether gcc supports -Wmissing-format-attribute... yes
checking whether g++ supports -Wundef... yes
checking whether g++ supports -Wno-long-long... yes
checking whether g++ supports -Wnon-virtual-dtor... yes
checking whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fno-common... yes
checking whether g++ supports -fexceptions... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -O0... yes
checking whether g++ supports -Wl,--no-undefined... yes
checking whether g++ supports -Wl,--allow-shlib-undefined... yes
not using lib directory suffix
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) 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 for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
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 for shl_load... (cached) no
checking for shl_load in -ldld... (cached) no
checking for dlopen... (cached) no
checking for dlopen in -ldl... (cached) yes
checking whether a program can dlopen itself... (cached) yes
checking whether a statically linked program can dlopen itself... (cached) yes
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for g77 option to produce PIC... -fPIC
checking if g77 PIC flag -fPIC works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes
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 for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking if C++ programs can be compiled... yes
checking for strlcat... no
checking if strlcat needs custom prototype... yes - in libkdefakes
checking for strlcpy... no
checking if strlcpy needs custom prototype... yes - in libkdefakes
checking for main in -lutil... yes
checking for main in -lcompat... no
checking for crypt in -lcrypt... yes
checking for socklen_t... yes
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for inet_ntoa... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for sys/types.h... (cached) yes
checking for stdint.h... (cached) yes
checking sys/bitypes.h usability... yes
checking sys/bitypes.h presence... yes
checking for sys/bitypes.h... yes
checking for poll in -lpoll... no
checking CoreAudio/CoreAudio.h usability... no
checking CoreAudio/CoreAudio.h presence... no
checking for CoreAudio/CoreAudio.h... no
checking if res_init needs -lresolv... yes
checking for res_init... yes
checking if res_init needs custom prototype... no
checking for killpg in -lucb... no
checking for int... yes
checking size of int... 4
checking for short... yes
checking size of short... 2
checking for long... yes
checking size of long... 4
checking for char *... yes
checking size of char *... 4
checking for dlopen in -ldl... (cached) yes
checking for shl_unload in -ldld... no
checking for size_t... yes
checking size of size_t... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking sizeof size_t == sizeof unsigned long... yes
checking crt_externs.h usability... no
checking crt_externs.h presence... no
checking for crt_externs.h... no
checking for _NSGetEnviron... no
checking for vsnprintf... yes
checking for snprintf... yes
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for IceConnectionNumber in -lICE... yes
checking for libXext... yes
checking for pthread_create in -lpthread... yes
checking for extra includes... no
checking for extra libs... no
checking for libz... -lz
checking for libpng... -lpng -lz -lm
checking for libjpeg6b... no
checking for libjpeg... -ljpeg
checking for perl... /usr/bin/perl
checking for Qt... configure: error: Qt (>= Qt 3.3) (headers and libraries) notfound. Please check your installation!
For more details about this problem, look at the end of config.log.
帮我看一下，什么错误，要安装什么东西？ 在GG上搜了一下
大都说是要装上qt-devel这个包 我去看一下，谢谢各位了，有问题再来问。 JAVA 版的，blackspace 能不能发个简单的安装和使用流程。 1) Install JRE from here.
2) Extract latest linux package (choice of GTK or Motif) from here
* To extract the program files from the package, type
o tar xvjf Azureus_x.x.x.x_linux...tar.bz2
where Azureus_x.x.x.x_linux...tar.bz2 is the name of the downloaded package.
3) Change to the azureus directory and run ./azureus to start
* cd azureus
* ./azureus
If you get an error message, or want to configure the java exec path, just open the azureus script file with your favorite text editor and edit the given configuration options.
If Azureus does not show up after a minute, you can try starting it manually:
* GTK:
o java -cp swt.jar:swt-pi.jar:Azureus2.jar -Djava.library.path=./ org.gudy.azureus2.ui.swt.Main
* Motif:
o java -cp swt.jar:Azureus2.jar -Djava.library.path=./ org.gudy.azureus2.ui.swt.Main
4) Please give feedback, if any exceptions were thrown. JRE是不是直接安装就行了吗？要不要指定目录什么的？ 每个发行版都不一样的说
System Requirements
See supported System Configurations for information about supported platforms, operating systems, desktop managers, and browsers.
For issues, see the Troubleshooting section below.
Installation Instructions
Installing the JDK automatically installs the Java Plugin and Java Web Start. Note that the Java Plugin needs to be registered with the browser. After installing the JDK, refer to:
* Java Plugin Browser Registration Instructions
* Java Web Start Installation Notes
Install formats - This version of the JDK is available in two installation formats.
* Self-extracting Binary File - This file can be used to install the JDK in a location chosen by the user. This one can be installed by anyone (not only root users), and it can easily be installed in any location. As long as you are not root user, it cannot displace the system version of the Java platform suppled by Linux. To use this file, see Installation of Self-Extracting Binary below.
* RPM Packages - A rpm.bin file containing RPM packages, installed with the rpm utility. Requires root access to install. RPM packages are the recommended method for installation on Linux. To use this bundle, see Installation of RPM File below.
Choose the install format that is most suitable to your needs.
Note: For any text on this page containing the following notation, you must substitute the appropriate JDK update version number for the notation.
<version>
For example, if you are downloading update 6_01, the following command:
./jdk-6_<version>-linux-i586.bin
would become:
./jdk-6_01-linux-i586.bin
Installation of Self-Extracting Binary
Use these instructions if you want to use the self-extracting binary file to install the JDK. If you want to install RPM packages instead, see Installation of RPM File.
1. Download and check the download file size to ensure that you have downloaded the full, uncorrupted software bundle.
You can download to any directory you choose; it does not have to be the directory where you want to install the JDK.
Before you download the file, notice its byte size provided on the download page on the web site. Once the download has completed, compare that file size to the size of the downloaded file to make sure they are equal.
2. Make sure that execute permissions are set on the self-extracting binary.
Run this command:
chmod +x jdk-6_<version>-linux-i586.bin
3. Change directory to the location where you would like the files to be installed.
The next step installs the JDK into the current directory.
4. Run the self-extracting binary.
Execute the downloaded file, prepended by the path to it. For example, if the file is in the current directory, prepend it with "./" (necessary if "." is not in the PATH environment variable):
./jdk-6_<version>-linux-i586.bin
The binary code license is displayed, and you are prompted to agree to its terms.
The JDK files are installed in a directory called jdk1.6.0_<version> in the current directory. Follow this link to see its directory structure. The JDK documentation is a separate download.
Note about Root Access: Unbundling the software automatically creates a directory called jdk1.6.0_<version>. Note that if you choose to install the JDK into system-wide location such as /usr/local, you must first become root to gain the necessary permissions. If you do not have root access, simply install the JDK into your home directory, or a subdirectory that you have permission to write to.
Note about Overwriting Files: If you unpack the software in a directory that contains a subdirectory named jdk1.6.0_<version>, the new software overwrites files of the same name in that jdk1.6.0_<version> directory. Please be careful to rename the old directory if it contains files you would like to keep.
Note about System Preferences: By default, the installation script configures the system such that the backing store for system preferences is created inside the JDK's installation directory. If the JDK is installed on a network-mounted drive, it and the system preferences can be exported for sharing with Java runtime environments on other machines.
See the Preferences API documentation for more information about preferences in the Java platform.
Installation of RPM File
Use these instructions if you want to install JDK in the form of RPM packages. If you want to use the self-extracting binary file instead, see Installation of Self-Extracting Binary.
1. Download and check the file size.
You can download to any directory you choose.
Before you download the file, notice its byte size provided on the download page on the web site. Once the download has completed, compare that file size to the size of the downloaded file to make sure they are equal.
2. Become root by running the su command and entering the super-user password.
3. Extract and install the contents of the downloaded file.
Change directory to where the downloaded file is located and run these commands to first set the executable permissions and then run the binary to extract and run the RPM file:
chmod a+x jdk-6_<version>-linux-i586-rpm.bin
./jdk-6_<version>-linux-i586-rpm.bin
Note that the initial "./" is required if you do not have "." in your PATH environment variable.
The script displays a binary license agreement, which you are asked to agree to before installation can proceed. Once you have agreed to the license, the install script creates and runs the file jdk-6_<version>-linux-i586.rpm in the current directory.
NOTE - If instead you want to only extract the RPM file but not install it, you can run the .bin file with the -x argument. You do not need to be root to do this.
4. Delete the bin and rpm file if you want to save disk space.
5. Exit the root shell.
The RPM packages creates two links /usr/java/latest and /usr/java/default.
* The /usr/java/latest link will always point to the version of Java that Sun Microsystems considers the latest version. Subsequent upgrades of the packages will overwrite this value if it is not the latest version.
* By default, /usr/java/default points to /usr/java/latest. However, if administrators change /usr/java/default to point to another version of Java, subsequent package upgrades will be provided by the administrators and cannot be overwritten.
When the JDK is installed, links to javac jar and javadoc are also created apart from the JRE links. These links point to the appropriate tool referenced by /usr/java/default. This allows the user to easily run the default version of these Java tools.
A new service script, named jexec, is added to /etc/init.d. This script allows users to directly execute any standalone JAR file that has an execution permission set. This can be demonstrated using an example from the JDK:
cd /usr/java/jdk1.6.0/demo/jfc/SwingSet2
chmod +x SwingSet2.jar
SwingSet2.jar
Java Plugin Browser Registration Instructions
You must register the Java Plugin product with Netscape or Mozilla for the Plugin to work. Click on the following link to see the instructions for manual registration. Note that for SuSE the 8.1 or higher version of Mozilla must be used, and for non-SuSE Linux, the version of Mozilla must be 1.1 or higher. Please follow these instructions:
Manual Registration Instructions
Also see documentation on the Java Plugin component.
Java Web Start Installation Notes
This JDK release includes Java Web Start; it is installed automatically with the JDK. But note the following:
* Compatibility: The release of Java Web Start that comes with this JDK/JRE can be run on SDK/JRE 1.2.2 or later. It will not work with SDK/JRE 1.1.x or earlier.
* Upgrading from Previous Versions: If you have a previous release of Java Web Start, do not uninstall it. Uninstalling it will cause the download cache to be cleared, and all previously installed Java Web Start applications will have to be downloaded again. This new release will overwrite previous installations and automatically update browsers to use this new release. The configuration files and program files folder used by Java Web Start have not changed, so all your settings will remain intact after the upgrade.
* Using Java Web Start with Netscape 6.x/7.x: For Netscape 6.x/7.x users, setup the Java Web Start MIME type (JNLP) in the Edit->Preferences->Navigator->Helper Applications section. The file extension is jnlp; MIME Type is application/x-java-jnlp-file. It should be handled by the javaws executable file in your Java Web Start directory. Also note that, due to a problem with the JavaScript in Netscape 6.x/7.x, you must use the non-JavaScript version of the demos page
Troubleshooting
* To print on Linux, the /usr/sbin/lpc utility must be installed. This is a standard Linux utility. On RedHat 7.1, for example, this utility is in the "LPRng-3.7.4-22 RPM" package.
页:
[1]