On 2011年09月23日 10:02, Bin Tian wrote:
Hi, all
On 2011年09月21日 22:06, Ian Lance Taylor wrote:
Stephen Kitt writes:
Is there a recommended approach to use to find dlltool using only
i686-w64-mingw32-gcc?
I don't know of one. I don't know why avoiding autoconf is desirable.
How
submit the bug, I think this isn't a bug.
We could do nothing and just wait multiarch to be ready. There will be
dlltool in /usr/$target/bin, isn't it?
Bin Tian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 2011年09月17日 20:58, Stephen Kitt wrote:
Hi Bill,
On Mon, 12 Sep 2011 21:54:44 +0200, Bill Allombert
wrote:
On Thu, Aug 04, 2011 at 08:36:52AM +0200, Stephen Kitt wrote:
On Wed, 29 Jun 2011 12:14:14 +0800, Bin Tian
wrote:
A possible resolution is to create symbol links for these tools
A possible resolution is to create symbol links for these tools in
/usr/lib/gcc/$target/$version or /usr/$target/bin
Or just specify the absolute path of these tools when configuring the
package.
Regards,
Bin Tian
On 2011年06月29日 11:55, Bin Tian wrote:
Package: gcc-mingw-w64
Version: 4.6.0
Package: gcc-mingw-w64
Version: 4.6.0-11
Severity: normal
The output of `i686-w64-mingw32-gcc --print-prog-name=ar` is ar, it is
obviously incorrect.
In fact, it gives wrong result for all tools except as and ld.
x86_64-w64-mingw32-gcc have the same problem.
Regards,
Bin Tian
-- System
key state after connected. due to the wrong process
of control key state in linuxvnc, you can't input any words.
Regards
Bin Tian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
us = %d\n", status);
};
ipvs1:~# gcc a.c
ipvs1:~# ./a.out
connect return -1
connect: : Network is unreachable
status = 0
ipvs1:~#
Bin Tian wrote:
> Package: keepalived
> Version: 1.1.15-1
> Severity: normal
>
> If you add an unreachable route to one realserver, the healthchecker doe
Package: keepalived
Version: 1.1.15-1
Severity: normal
If you add an unreachable route to one realserver, the healthchecker doesn't
remove the realserver.
For example,
# ip ro add unreachable 10.1.8.48
# telnet 10.1.8.48 80
Trying 10.1.8.48...
telnet: Unable to connect to remote host: Network
' command
Please correct it.
Regards,
Bin Tian
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (char
If libiptc.h will not be included in iptables-dev, please remove the
line `#include "libiptc/libiptc.h"` from iptables.h when packging.
Best regards,
Bin Tian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: libsnmp9
Version: 5.2.3-7
Severity: normal
On AMD64 system, when parsing a counter64 variable, it will output
something like that:
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bits (6)
truncating unsigned value to 32 bi
patched.
Bin Tian
Bin Tian wrote:
> I got the acknowledgement. The reference is bug#410066
>
> Bin Tian
>
> Bin Tian wrote:
>> I found the problem. gcc-4.1 under ppc behaves differently for the
>> default signedness of char. I have already reported this bug to
>> [
pprently this problem exists in the gcc which debian building system
is using.
There may be other packages affected by this problem.
Best Regards,
Bin Tian
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shel
I tried but it doesn't work.
Backtrace of fcitx is attached as bellow. It may be helpful.
Best Regards
Bin Tian.
~$ gdb -p 4821
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welco
fcitx on debian amd64 is ok.
Bin Tian wrote:
I checked the bugs list of fcitx. The removal of ~/.fcitx directory which
mentioned in bug #392740 doesn't work.
Best regards
Bin Tian
Bin Tian wrote:
Package: fcitx
Version: 1:3.4-1
Severity: grave
Justification: renders package unusabl
I checked the bugs list of fcitx. The removal of ~/.fcitx directory which
mentioned in bug #392740 doesn't work.
Best regards
Bin Tian
Bin Tian wrote:
Package: fcitx
Version: 1:3.4-1
Severity: grave
Justification: renders package unusable
Hi,
I'm using debian on my iBook-G4
board stike
will casue fcitx crashed. The problem exists for more than 3 months, and
I have to downgrade fcitx to sarge version.
If you needs more information, please let me know.
Best Regards
Bin Tian
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, &#x
file:/small/xen-disks/
debian/swap.img,hdb,w','file:/home/sparrow/PlanetLab-BootCD-3.3.iso,hdc:cdrom,r'
,'file:/home/sparrow/boot,fda:floppy,r' ]
My HVM
domU works again.
Thanks a lot! ;)
Best regards,
BinTian
Bastian Blank wrote:
On Thu, Sep 28, 2006 at 02:51:48PM +080
Bastian Blank wrote:
On Thu, Sep 28, 2006 at 02:51:48PM +0800, Bin Tian wrote:
I find that the qemu-ifup is very simple, so I make a copy of qemu-ifup
in /etc/xen/ directory. This time, the domU started and I saw the boot
screen of BIOS in vncviewer. But the BIOS said:
CDROM
x27;m sure that the iso file is well. And I tried to start another domU
which runs windows, and got the same result: CDROM boot failure.
regards,
Bin Tian.
Bin Tian wrote:
Thanks
for
your quick response.
The package xen-utils-common is already 3.0+hg11624-1. And I make some
correction i
fup
/etc/xen/qemu-ifup
I think that qemu-dm should be patched.
Best regards,
Bin Tian
Bastian Blank wrote:
On Thu, Sep 28, 2006 at 09:26:06AM +0800, Bin Tian wrote:
The HVM domU won't start. The following is the config (comments
stripped).
Please check for the existance
The
xend.log may be helpful.
Best regards,
Bin Tian
Debian Bug Tracking System wrote:
Thank you for the problem report you have sent regarding Debian.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the package
Package: xen-hypervisor-3.0-unstable-1-amd64
Version: 3.0-unstable+hg11561-1
Severity: important
The HVM domU won't start. The following is the config (comments
stripped).
begin
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir =
-3.0-unstable-1 3.0-unstable+hg11561-1 XEN administrative tools
ii xen-utils-common 3.0+hg11624-1 XEN administrative tools - common files
[EMAIL PROTECTED]:~$ /sbin/ifconfig -a | egrep "veth|vif"
[EMAIL PROTECTED]:~$
Best regards,
Bin Tian
Debian Bug Tracking System wrote:
> This is
Sorry for giving some wrong information. The version of
xen-hypervisor-3.0-amd64
I installed is 3.0.2-3-hg9762-1, not 3.0.2-hg9697-2.
Bin Tian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ENadministrative tools - common files
I think it's not a nlookbacks problem, because everything is the default
installation. And before installing xen unstable, I purged the installed
xen-hyphervisor-3.0-amd64 packages.
Best regards,
Bin Tian
-- System Information:
Debian Release: testin
Package: subversion
Version: 1.4.0-2
Severity: normal
When I run svnadmin help in shell, it told me that
svnadmin: Bad database version: compiled with 4.4.20, running against
4.3.29
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Archit
27 matches
Mail list logo
