[Solved] scim-bridge - pkgbuild trouble

Leigh · 2009-04-22 11:40:20

I submitted scim-bridge 0.4.15 quite some time ago and there's been two versions updates since then. I've been fumbling around trying to update this for the past two versions with little progress. I'm pretty sure gcc43 needs patched as well as qt4. The only examples of the patches I can find is from a recent gentoo ebuild, and the gcc43 and qt4 patch files, used in the ebuild, found here, which don't seem to work when applying to a pkgbuild. I'm not that great with pkgbuilds and probably shouldn't be the maintainer of something quite a few archers seem to be using. I feel like I'm letting them down!
Can someone help me update this to scim-bridge 0.4.16?

The latest working pkgbuild is for version 0.4.15, in aur...

# Contributor
# Maintainer: Leigh <leigh@archlinux.us>

pkgname=scim-bridge
pkgver=0.4.15
pkgrel=1
pkgdesc="scim-bridge IM-client for SCIM"
arch=('i686' 'x86_64')
url="http://www.scim-im.org/projects/scim_bridge"
license=('GPL' 'LGPL')
depends=('scim')
makedepends=('doxygen' 'qt4')
source=(http://downloads.sourceforge.net/sourceforge/scim/$pkgname-$pkgver.tar.gz)
md5sums=('03015dfdc01f8aa6ad933c695f47077b')
build() {
  cd "$startdir/src/$pkgname-$pkgver"
  sed -i -e 's|/plugins|/lib/qt/plugins|g' client-qt/qt4/Makefile.{in,am} || return 1
  ./configure --prefix=/usr \
              --enable-agent \
              --enable-qt4-immodule \
              --disable-qt3-immodule \
              --enable-gtk2-immodule
  make || return 1
  make DESTDIR="$startdir/pkg" install
}

Last edited by Leigh (2009-05-13 19:55:13)

Snowman · 2009-04-22 19:54:12

Untested. The patch are from the Gentoo link you posted. You'll need to update the md5sums. The sed line might not be needed anymore (I've commented it).
Compare my changes with the ebuild. It might help you the next time you need to do something similar.

pkgname=scim-bridge
pkgver=0.4.16
pkgrel=1
pkgdesc="scim-bridge IM-client for SCIM"
arch=('i686' 'x86_64')
url="http://www.scim-im.org/projects/scim_bridge"
license=('GPL' 'LGPL')
depends=('scim')
makedepends=('doxygen' 'qt4')
source=(http://downloads.sourceforge.net/sourceforge/scim/$pkgname-$pkgver.tar.gz scim-bridge-0.4.15.2-gcc43.patch scim-bridge-0.4.15.2-qt4.patch  )
md5sums=('03015dfdc01f8aa6ad933c695f47077b')
build() {
  cd "$startdir/src/$pkgname-$pkgver"

patch -p1 < ../scim-bridge-0.4.15.2-qt4.patch || return 1
patch -p1 < ../scim-bridge-0.4.15.2-gcc43.patch || return 1

#  sed -i -e 's|/plugins|/lib/qt/plugins|g' client-qt/qt4/Makefile.{in,am} || return 1

    intltoolize --force
    autoreconf

  ./configure --prefix=/usr \
              --enable-agent \
              --enable-qt4-immodule \
              --disable-qt3-immodule \
              --enable-gtk2-immodule
  make || return 1
  make DESTDIR="$startdir/pkg" install
}

Leigh · 2009-04-22 22:58:42

Thank you snowman!

I been struggling so much with this and have tried so many things. Removing the sed line was one of the first things I tried, and also tried adding the intltoolize --force and autoreconf lines on a few attempts. but can't remember if I used those two lines with or without the sed line. I'll give your pkgbuild a try in the morning after work, and hopefuly I can finally get this updated in aur.

It would be nice to understand ebuilds better. They are so different to pkgbuilds and really confuse me!

Leigh · 2009-04-23 07:41:54

Still getting the all-recursive error at the end of the build. Seems to be associated with libtool.

../libtool: line 838: X--tag=CC: command not found
../libtool: line 871: libtool: ignoring unknown tag : command not found
../libtool: line 838: X--mode=compile: command not found
../libtool: line 838: X--tag=CC: command not found
../libtool: line 871: libtool: ignoring unknown tag : command not found
../libtool: line 838: X--tag=CC: command not found
../libtool: line 838: X--tag=CC: command not found
../libtool: line 871: libtool: ignoring unknown tag : command not found
../libtool: line 838: X--mode=compile: command not found
../libtool: line 1005: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 1006: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
../libtool: line 1149: Xgcc: command not found
../libtool: line 838: X--mode=compile: command not found
../libtool: line 871: libtool: ignoring unknown tag : command not found
../libtool: line 1005: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 838: X--mode=compile: command not found
../libtool: line 1006: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
../libtool: line 1149: Xgcc: command not found
../libtool: line 1149: X-DHAVE_CONFIG_H: command not found
../libtool: line 1149: X-I.: command not found
../libtool: line 1149: X-DHAVE_CONFIG_H: command not found
../libtool: line 1005: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 1006: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
../libtool: line 1149: Xgcc: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1149: X-I.: command not found
../libtool: line 1149: X-DHAVE_CONFIG_H: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1005: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 1149: X-I.: command not found
../libtool: line 1006: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1149: Xgcc: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1149: X-I/usr/include/scim-1.0: No such file or directory
../libtool: line 1149: X-I/usr/include/scim-1.0: No such file or directory
../libtool: line 1149: X-DHAVE_CONFIG_H: command not found
../libtool: line 1149: X-march=nocona: command not found
../libtool: line 1149: X-march=nocona: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1149: X-I.: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1149: X-mtune=nocona: command not found
../libtool: line 1149: X-I/usr/include/scim-1.0: No such file or directory
../libtool: line 1149: X-O2: command not found
../libtool: line 1149: X-march=nocona: command not found
../libtool: line 1149: X-mtune=nocona: command not found
../libtool: line 1149: X-pipe: command not found
../libtool: line 1149: X-O2: command not found
../libtool: line 1149: X-mtune=nocona: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1149: X-pipe: command not found
../libtool: line 1149: X-O2: command not found
../libtool: line 1149: X-fomit-frame-pointer: command not found
../libtool: line 1149: X-pipe: command not found
../libtool: line 1149: X-fomit-frame-pointer: command not found
../libtool: line 1149: X-I..: command not found
../libtool: line 1149: X-I/usr/include/scim-1.0: No such file or directory
../libtool: line 1149: X-MT: command not found
../libtool: line 1149: X-fomit-frame-pointer: command not found
../libtool: line 1149: X-MT: command not found
../libtool: line 1149: X-march=nocona: command not found
../libtool: line 1149: Xlibscimbridgecommon_la-scim-bridge-display.lo: command not found
../libtool: line 1149: X-MT: command not found
../libtool: line 1149: X-MD: command not found
../libtool: line 1149: X-mtune=nocona: command not found
../libtool: line 1149: Xlibscimbridgecommon_la-scim-bridge-key-event.lo: command not found
../libtool: line 1149: X-MP: command not found
../libtool: line 1149: X-O2: command not found
../libtool: line 1149: Xlibscimbridgecommon_la-scim-bridge-attribute.lo: command not found
../libtool: line 1149: X-MD: command not found
../libtool: line 1149: X-MP: command not found
../libtool: line 1149: X-MF: command not found
../libtool: line 1149: X-pipe: command not found
../libtool: line 1149: X-MF: command not found
../libtool: line 1149: X-MD: command not found
../libtool: line 1149: X.deps/libscimbridgecommon_la-scim-bridge-display.Tpo: No such file or directory
../libtool: line 1149: X-c: command not found
../libtool: line 1149: X-MP: command not found
../libtool: line 1149: X.deps/libscimbridgecommon_la-scim-bridge-attribute.Tpo: No such file or directory
../libtool: line 1149: X-MF: command not found
../libtool: line 1202: Xlibscimbridgecommon_la-scim-bridge-display.lo: command not found
../libtool: line 1149: X.deps/libscimbridgecommon_la-scim-bridge-key-event.Tpo: No such file or directory
../libtool: line 1149: X-fomit-frame-pointer: command not found
../libtool: line 1149: X-c: command not found
../libtool: line 1207: libtool: compile: cannot determine name of library object from `': command not found
make[2]: *** [libscimbridgecommon_la-scim-bridge-display.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
../libtool: line 1202: Xlibscimbridgecommon_la-scim-bridge-attribute.lo: command not found
../libtool: line 1149: X-c: command not found
../libtool: line 1149: X-MT: command not found
../libtool: line 1207: libtool: compile: cannot determine name of library object from `': command not found
make[2]: *** [libscimbridgecommon_la-scim-bridge-attribute.lo] Error 1
../libtool: line 1202: Xlibscimbridgecommon_la-scim-bridge-key-event.lo: command not found
../libtool: line 1149: Xlibscimbridgecommon_la-scim-bridge-path.lo: command not found
../libtool: line 1207: libtool: compile: cannot determine name of library object from `': command not found
make[2]: *** [libscimbridgecommon_la-scim-bridge-key-event.lo] Error 1
../libtool: line 1149: X-MD: command not found
../libtool: line 1149: X-MP: command not found
../libtool: line 1149: X-MF: command not found
../libtool: line 1149: X.deps/libscimbridgecommon_la-scim-bridge-path.Tpo: No such file or directory
../libtool: line 1149: X-c: command not found
../libtool: line 1202: Xlibscimbridgecommon_la-scim-bridge-path.lo: command not found
../libtool: line 1207: libtool: compile: cannot determine name of library object from `': command not found
make[2]: *** [libscimbridgecommon_la-scim-bridge-path.lo] Error 1
make[2]: Leaving directory `/home/lianli/build/scim-bridge/src/scim-bridge-0.4.16/common'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/lianli/build/scim-bridge/src/scim-bridge-0.4.16'
make: *** [all] Error 2
==> ERROR: Build Failed.

One error at the beginning...

ERROR: 'IT_PROG_INTLTOOL' must appear in configure.ac for intltool to work.

Same errors whether i build with or without the sed line.
Also with or without the lines...
intltoolize --force
autoreconf

At this point I'm just guessing and doing trial and error stuff. I tried downgrading libtool and that didn't help. I'll keep fiddling and searching, but can't find much info about the latest 0.4.16. It seems most distros are still using 0.4.15 or earlier.

tdy · 2009-04-23 08:26:14

Not 100% sure, but it seems to be an x86_64 issue. On my i686 laptop, I just bumped the vers/md5 on your 0.4.15 PKGBUILD and it compiled with no issues. On my x86_64 desktop, none of the PKGBUILDs in this thread have worked for me (I get the same libtool errors as you).

Leigh · 2009-04-23 10:43:08

I should have mentioned I was running x86_64. Anyway, I'm able to build the 0.4.15 version using the pkgbuild in my original post (same as what is in aur) with no problems. The trouble started with the last two version updates, 0.4.15.2 and latest.

Snowman · 2009-04-24 02:01:38

try adding:
libtoolize --force --copy || return 1
before autoreconf.

Leigh · 2009-04-24 08:32:54

Snowman wrote:

try adding:
libtoolize --force --copy || return 1
before autoreconf.

Seems to take care of the libtool errors, and the build, I think, gets a little further, but then fails with the below errors.

Also I don't think the sed line is needed. With or without that line, the build always stops at the same place with the same errors.

I ran ./configure --help to maybe find a option to tell config to look for the missing files in the right place, but I'm not sure they even exist yet. Need sleep! will experiment some more tomorrow.

../im-scim-bridge-qt.cpp:28:33: error: qinputcontextplugin.h: No such file or directory
In file included from ../scim-bridge-client-imcontext-qt.cpp:39:
../scim-bridge-client-imcontext-qt.h:42:27: error: qinputcontext.h: No such file or directory
In file included from ../scim-bridge-client-qt.h:38,
                 from ../scim-bridge-client-qt.cpp:24:
../scim-bridge-client-imcontext-qt.h:42:27: error: qinputcontext.h: No such file or directory
In file included from ../im-scim-bridge-qt.cpp:33:
../scim-bridge-client-imcontext-qt.h:42:27: error: qinputcontext.h: No such file or directory
In file included from ../scim-bridge-client-qt.h:38,
                 from ../scim-bridge-client-qt.cpp:24:
../scim-bridge-client-imcontext-qt.h:60: error: expected class-name before '{' token
../scim-bridge-client-imcontext-qt.h:179: error: 'ButtonState' has not been declared
../scim-bridge-client-imcontext-qt.h:179: error: 'ButtonState' has not been declared
In file included from ../im-scim-bridge-qt.cpp:33:
../scim-bridge-client-imcontext-qt.h:60: error: expected class-name before '{' token
../scim-bridge-client-imcontext-qt.h:179: error: 'ButtonState' has not been declared
../scim-bridge-client-imcontext-qt.h:179: error: 'ButtonState' has not been declared
../im-scim-bridge-qt.cpp:41: error: expected class-name before '{' token
../im-scim-bridge-qt.cpp:62: error: ISO C++ forbids declaration of 'QInputContext' with no type
../im-scim-bridge-qt.cpp:62: error: expected ';' before '*' token
../im-scim-bridge-qt.cpp:110: error: expected constructor, destructor, or type conversion before '*' token
In file included from ../scim-bridge-client-imcontext-qt.cpp:39:
../scim-bridge-client-imcontext-qt.h:60: error: expected class-name before '{' token
../scim-bridge-client-imcontext-qt.h:179: error: 'ButtonState' has not been declared
../scim-bridge-client-imcontext-qt.h:179: error: 'ButtonState' has not been declared
make[2]: *** [im_scim_bridge_la-im-scim-bridge-qt.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
../scim-bridge-client-imcontext-qt.cpp:83: error: 'ButtonState' has not been declared
../scim-bridge-client-imcontext-qt.cpp:83: error: 'ButtonState' has not been declared
../scim-bridge-client-imcontext-qt.cpp:306: error: 'ButtonState' has not been declared
../scim-bridge-client-imcontext-qt.cpp:306: error: 'ButtonState' has not been declared
make[2]: *** [im_scim_bridge_la-scim-bridge-client-qt.lo] Error 1
../scim-bridge-client-imcontext-qt.cpp: In member function 'virtual void ScimBridgeClientIMContextImpl::reset()':
../scim-bridge-client-imcontext-qt.cpp:395: error: 'QInputContext' has not been declared
../scim-bridge-client-imcontext-qt.cpp: In member function 'void ScimBridgeClientIMContextImpl::commit()':
../scim-bridge-client-imcontext-qt.cpp:482: error: 'isComposing' was not declared in this scope
../scim-bridge-client-imcontext-qt.cpp:489: error: 'sendIMEvent' was not declared in this scope
../scim-bridge-client-imcontext-qt.cpp:490: error: 'sendIMEvent' was not declared in this scope
../scim-bridge-client-imcontext-qt.cpp: In member function 'void ScimBridgeClientIMContextImpl::update_preedit()':
../scim-bridge-client-imcontext-qt.cpp:668: error: 'isComposing' was not declared in this scope
../scim-bridge-client-imcontext-qt.cpp:668: error: 'sendIMEvent' was not declared in this scope
../scim-bridge-client-imcontext-qt.cpp:676: error: 'sendIMEvent' was not declared in this scope
../scim-bridge-client-imcontext-qt.cpp:678: error: 'isComposing' was not declared in this scope
../scim-bridge-client-imcontext-qt.cpp:678: error: 'sendIMEvent' was not declared in this scope
../scim-bridge-client-key-event-utility-qt.cpp: In function 'void static_initialize()':
../scim-bridge-client-key-event-utility-qt.cpp:136: error: 'Key_Multi_key' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:137: error: 'Key_Codeinput' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:138: error: 'Key_SingleCandidate' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:139: error: 'Key_MultipleCandidate' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:140: error: 'Key_PreviousCandidate' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:141: error: 'Key_Mode_switch' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:142: error: 'Key_Kanji' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:143: error: 'Key_Muhenkan' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:144: error: 'Key_Henkan' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:145: error: 'Key_Romaji' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:146: error: 'Key_Hiragana' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:147: error: 'Key_Katakana' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:148: error: 'Key_Hiragana_Katakana' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:149: error: 'Key_Zenkaku' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:150: error: 'Key_Hankaku' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:151: error: 'Key_Zenkaku_Hankaku' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:152: error: 'Key_Touroku' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:153: error: 'Key_Massyo' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:154: error: 'Key_Kana_Lock' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:155: error: 'Key_Kana_Shift' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:156: error: 'Key_Eisu_Shift' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:157: error: 'Key_Eisu_toggle' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:158: error: 'Key_Hangul' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:159: error: 'Key_Hangul_Start' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:160: error: 'Key_Hangul_End' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:161: error: 'Key_Hangul_Hanja' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:162: error: 'Key_Hangul_Jamo' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:163: error: 'Key_Hangul_Romaja' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:164: error: 'Key_Hangul_Jeonja' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:165: error: 'Key_Hangul_Banja' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:166: error: 'Key_Hangul_PreHanja' is not a member of 'Qt'
../scim-bridge-client-key-event-utility-qt.cpp:167: error: 'Key_Hangul_Special' is not a member of 'Qt'
make[2]: *** [im_scim_bridge_la-scim-bridge-client-imcontext-qt.lo] Error 1
make[2]: *** [im_scim_bridge_la-scim-bridge-client-key-event-utility-qt.lo] Error 1
make[2]: Leaving directory `/home/lianli/build/scim-bridge/src/scim-bridge-0.4.16/client-qt/qt3'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/lianli/build/scim-bridge/src/scim-bridge-0.4.16'
make: *** [all] Error 2

Last edited by Leigh (2009-04-24 08:34:56)

Snowman · 2009-04-24 21:12:04

uninstall qt3 or build it in a chroot and it will work. The problem is that it detects qt3 and tries to build with it. As you disabled it with the configure option, it's not set to build properly. It's a bug with their build system.

You should replace the qt4 makedepends to qt.

Replace $startdir/src by $srcdir
and $startdir/pkg by $pkgdir

Leigh · 2009-04-24 23:24:55

Ok, will try in the morning. Gentoo's ebuild is starting to make better sense now. I wonder if I could set this up in such a way that if qt3 is detected on the sysytem, to build for qt3, otherwise default to qt4? Or something more similar to gentoo's ebuild.

I caught the qt4 in make depends the other night realizing it should be qt. I'm thinking even if this builds with no qt3 present, it might be better to keep version 0.4.15 in aur until the bug gets fixed, that way people can still keep qt3 along side qt4 and still use scim-bridge.

Snowman · 2009-04-26 21:32:04

Leigh wrote:

Ok, will try in the morning. Gentoo's ebuild is starting to make better sense now. I wonder if I could set this up in such a way that if qt3 is detected on the sysytem, to build for qt3, otherwise default to qt4? Or something more similar to gentoo's ebuild.

try removing:
--disable-qt3-immodule
that might do that.

Leigh wrote:

I caught the qt4 in make depends the other night realizing it should be qt. I'm thinking even if this builds with no qt3 present, it might be better to keep version 0.4.15 in aur until the bug gets fixed, that way people can still keep qt3 along side qt4 and still use scim-bridge.

I don't see any reason to do that. After building, just reinstall qt3 and everything will work. Just post a comment in AUR to warn users about it.

Leigh · 2009-04-27 20:11:51

I'm still messing around with this. My system is very dependent on qt3 and I'm wanting to avoid having to remeove qt3 in order to build this. It won't build with exsisting qt3 unless I rebuild qt3 with a qinput (can't remember the exact name) patch, which I'm having a little trouble with. It just seems odd to me that since qt4 is in a totally seperate location from qt3 that this won't build for qt4 with qt3 present. Maybe this is a sign that qt3 is getting closer to becomming obsolete.

Snowman · 2009-04-27 21:59:34

A chroot would work here.

There might be a way to make it work without using a chroot and with qt3 installed. The problem is that it tries to build qt4 stuff by using the location of the qt3 include files. That's why you get "error: qinputcontextplugin.h: No such file or directory" and similar errors. It'll require using some configure options or patching the Makefile so it knows where the qt4 include files are located. I could take a look.

Leigh · 2009-04-28 05:02:54

Thanks. I kind of figured this out. There are configure options that I think will work. Fixing this is teaching me a few things even though it's taking me a while. It's tuff finding time during the week. My boss is being a total slave driver! *sigh*

Snowman · 2009-04-28 07:02:56

FYI, this Gentoo bug explains the problem: http://bugs.gentoo.org/265872

Leigh · 2009-04-28 23:00:41

Snowman wrote:

FYI, this Gentoo bug explains the problem: http://bugs.gentoo.org/265872

Thanks for finding that info snowman! Ugh, all my searching never pulled that bug up. Should be relatively easy to fix.

edit..
Maybe not so easy to fix. Will build if qt3 is not installed, or should build by default for qt3, if qt3 is patched with latest qt-x11-immodule-unified-qt3 patch, but havent tested.

Last edited by Leigh (2009-05-01 06:35:11)

Leigh · 2009-05-13 10:14:23

Finally updated in aur.

http://aur.archlinux.org/packages.php?ID=20294

Arch Linux

#1 2009-04-22 11:40:20

[Solved] scim-bridge - pkgbuild trouble

#2 2009-04-22 19:54:12

Re: [Solved] scim-bridge - pkgbuild trouble

#3 2009-04-22 22:58:42

Re: [Solved] scim-bridge - pkgbuild trouble

#4 2009-04-23 07:41:54

Re: [Solved] scim-bridge - pkgbuild trouble

#5 2009-04-23 08:26:14

Re: [Solved] scim-bridge - pkgbuild trouble

#6 2009-04-23 10:43:08

Re: [Solved] scim-bridge - pkgbuild trouble

#7 2009-04-24 02:01:38

Re: [Solved] scim-bridge - pkgbuild trouble

#8 2009-04-24 08:32:54

Re: [Solved] scim-bridge - pkgbuild trouble

#9 2009-04-24 21:12:04

Re: [Solved] scim-bridge - pkgbuild trouble

#10 2009-04-24 23:24:55

Re: [Solved] scim-bridge - pkgbuild trouble

#11 2009-04-26 21:32:04

Re: [Solved] scim-bridge - pkgbuild trouble

#12 2009-04-27 20:11:51

Re: [Solved] scim-bridge - pkgbuild trouble

#13 2009-04-27 21:59:34

Re: [Solved] scim-bridge - pkgbuild trouble

#14 2009-04-28 05:02:54

Re: [Solved] scim-bridge - pkgbuild trouble

#15 2009-04-28 07:02:56

Re: [Solved] scim-bridge - pkgbuild trouble

#16 2009-04-28 23:00:41

Re: [Solved] scim-bridge - pkgbuild trouble

#17 2009-05-13 10:14:23

Re: [Solved] scim-bridge - pkgbuild trouble

Board footer