Custom Query (2447 matches)
Results (502 - 504 of 2447)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#46 | WontFix | change default PREFIX to /usr/local | ||
Description |
Since most projects do it this way and to not interfere with software managed by the system under /usr, I would suggest to change the default install PREFIX to /usr/local. |
|||
#58 | WontFix | Wizard doesn't support 448 Kbits/second upload line speed | ||
Description |
Debian bug report: From: Matt Kraai <kraai@ftbfs.org> To: submit@bugs.debian.org Subject: Wizard doesn't support 448 Kbits/second upload line speed Date: Sun, 24 Feb 2008 14:39:14 -0800 Package: deluge-torrent Version: 0.5.8.4-1 My upload line speed is 448 kbits/second, but Deluge's configuration wizard only provides options for 384 kbits/second and 512 kbits/second. It would be nice if the wizard supported arbitrary speeds. -- Matt |
|||
#62 | WontFix | Linker Error with Hardened GCC-3.4.6-r2 | ||
Description |
I get the following error when trying to compile from source (using the Gentoo ebuild): `.L55274' referenced in section `.gnu.linkonce.r._ZN4asio19asio_handler_invokeINS_6detail16resolver_serviceINS_2ip3tcpEE21resolve_query_handlerIN5boost3_bi6bind_tIvNS7_4_mfi3mf3IvN10libtorrent13socks5_streamERKNS_10error_codeENS3_23basic_resolver_iteratorIS4_EENS7_10shared_ptrINS7_8functionIFvSG_ESaIvEEEEEEENS8_5list4INS8_5valueIPSD_EEPFNS7_3argILi1EEEvEPFNSU_ILi2EEEvENSR_ISO_EEEEEEEEEEvT_z' of build/temp.linux-i686-2.5/libtorrent/src/http_tracker_connection.o: defined in discarded section `.gnu.linkonce.t._ZN4asio19asio_handler_invokeINS_6detail16resolver_serviceINS_2ip3tcpEE21resolve_query_handlerIN5boost3_bi6bind_tIvNS7_4_mfi3mf3IvN10libtorrent13socks5_streamERKNS_10error_codeENS3_23basic_resolver_iteratorIS4_EENS7_10shared_ptrINS7_8functionIFvSG_ESaIvEEEEEEENS8_5list4INS8_5valueIPSD_EEPFNS7_3argILi1EEEvEPFNSU_ILi2EEEvENSR_ISO_EEEEEEEEEEvT_z' of build/temp.linux-i686-2.5/libtorrent/src/http_tracker_connection.o I'm using the hardened toolchain, which hasn't upgraded to GCC 4.x yet :(. This could very well be a GCC 3.x bug but I thought I'd document it here. $ gcc -v Reading specs from /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/specs Configured with: /var/tmp/portage/sys-devel/gcc-3.4.6-r2/work/gcc-3.4.6/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.4.6 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.4.6 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.4.6/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.4.6/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/include/g++-v3 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --enable-java-awt=gtk --with-arch=i686 --enable-languages=c,c++,java,treelang,f77 --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 3.4.6 (Gentoo Hardened 3.4.6-r2 p1.5, ssp-3.4.6-1.0, pie-8.7.10) |