Hi,
I'm an upstream maintainer of the project (code.google.com/p/mozc). We're aware of the issue and now trying to fix the upstream code. For now, could you try the attached patch?
patch description:
g++ 4.6 on Oneiric seems to be more strict than others. For example, if we use 'g++ -lXXX -o binary_name *.o', g++ sometimes fails to link due to undefined references even when libXXX is a shared library. On this environment, it seems that we always have to pass the command line parameters in this order: 'g++ -o binary_name *.o -lXXX'.
Hi, com/p/mozc) . We're aware of the issue and now trying to fix the upstream code. For now, could you try the attached patch?
I'm an upstream maintainer of the project (code.google.
patch description:
g++ 4.6 on Oneiric seems to be more strict than others. For example, if we use 'g++ -lXXX -o binary_name *.o', g++ sometimes fails to link due to undefined references even when libXXX is a shared library. On this environment, it seems that we always have to pass the command line parameters in this order: 'g++ -o binary_name *.o -lXXX'.
The patch fixes the order.