Linux下Pidgin的QQ登录问题
星期六, 09月 15, 2007 2:36
昨天才下的Pidgin 2.1.1 装上，因为之前反应老版本登录QQ会提示密码错误而无法登录，所以找了一下解决办法如下：
把header_info.h文件中的 #define QQ_CLIENT 0x0f15 改为：
#define QQ_CLIENT 0x0E1B
后来发现这个版本的Pidgin已经做了相应修改，于是直接装上。结果MSN和Gtalk都可以，而QQ的问题依旧，看来TC又“更新”它的QQ版本号了。 Gtalk和MSN都将其在Linux下的实现交给了开源社区，而TC的这种行事实在不敢恭维——干嘛那么无聊呢 ？ 反正没几天又会有人能解决这种问题，TC逗我们玩啦 。今天看到Pidgin的2.2.0版本又出来了，期待可以解决这个问题。先卸下昨天才装的旧版本，如果编译目录还在的话，进入编译目录，然后执行：
将Pidgin顺利卸载，如果目录被删除 再重新编译安装一次再uninstall，虽然有点麻烦，不过可以避免一些问题。
下面开始安装新版本，步骤如下（在终端下执行）：
cd pidgin-2.2.0 －－进入编译目录
./configure －－ 这个过程完后会出现各种错误信息，下面会讲到
make －－ 编译软件包，过程有些长
make check －－（可选，程序包自检）
sudo make install －－进行软件包的安装
如果 ./configure 后出现错误信息，在Ubuntu下用 make 编译时就会“找不到Makefile”。解决办法如下： eg. 在 ./configure 后出现错误：
根据错误提示 用新得立软件包管理器 搜索 GLib 2.0 或者 直接用命令
这样系统会列出很多与缺少的Glib 2.0 有关的包文件。找到-dev结尾的包如这里是： libglib2.0-dev - Development files for the GLib library ，根据文件名执行安装。
用同样的方法查找到缺少的包 并安装直到 ./configure 不再出现错误信息，这时候就可以顺利 make／make install 了。
完成了2.2.0的安装，发现QQ还是不能用——“密码不对。Pidgin 将不会尝试重新连接账户，除非您纠正了错误然后重新启用账户。”不过既然有新版了，还是推荐更新一下了：
12月 1st, 2007 at 9:17 星期六
参考(Pidgin 2.3.0 附的安装/卸载说明)
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, a file `config.cache' that saves the results of its tests to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure').
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 at some point `config.cache' contains results you don't want to keep, you may remove or edit it.
The file `configure.ac' 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. If it finishes successfully, it will print out of a summary of the build options. This summary will also appear in the help->about dialog.
2. Type `make' to compile the package. On some systems, you may need to use `gmake' instead.
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. You must have write access to the prefix you are installing to. See below for more details on the prefix.
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.
6. If you have *not* run make distclean, you can use the target `make uninstall` to remove the files installed by `make install`.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the `configure' script does not know about. You can give `configure' initial values for variables by setting them in the environment. Using a Bourne-compatible shell, you can do that on the command line like
this: CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
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 supports 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.
。。。。。。。。
[Reply]
12月 1st, 2007 at 9:46 星期六
Pidgin已经更新到2.3了，但对QQ的支持还是不好，我的7位QQ从没成功登陆过。所以目前不能将它作为Linux下QQ的解决之道。
除此以外还有LumaQQ（下载及使用参看这里）用得比较广泛，它的开发到2006版滞了，但05版以后的还是可以使用；
或者也可以利用Wine（已更新到0.9.49） 直接在Linux下安装QQ 2007（具体实现可以参看这里）。
[Reply]