Installing Mozc on my MacBook without it burning down [SOLVED]

adr77 · 2024-06-22 00:18:25

This is just a simple question that'd I would like answered, related to my MacBook7,1:

Because of the fact that it gets so hot and slow, I would like to get help on how can I install the Mozc module for fcitx5 from the AUR without burning my house down by compiling it on my MacBook? I have the monolith to help out, if there is a good guide or someone here that can tell me; how can I compile fcitx5's Mozc module without compiling it on the device I'm installing it on?

Cheers!

note: Just compile it from a desktop, unless all you got is a MacBook7,1, and I wish you godspeed compiling stuff on it.

Last edited by adr77 (2024-06-23 14:11:37)

seth · 2024-06-22 06:21:53

build the package on a second system w/ an updated arch system, carry it over and "pacman -U" it
move to the arctic
limit the cpu load of the build (either the amount of jobs, thus used cores: https://wiki.archlinux.org/title/Makepk … uild_times or w/ https://aur.archlinux.org/packages/cpulimit )
don't build houses out of hay, that's a really bad concept (there's a story about three little pigs explaining why)
why are you trying to build the package itfp? https://archlinux.org/packages/extra/x8 … itx5-mozc/
get a bigger fan
address the general heat issues of the system

Last edited by seth (2024-06-22 06:22:37)

adr77 · 2024-06-22 11:10:25

seth wrote:

build the package on a second system w/ an updated arch system, carry it over and "pacman -U" it
move to the arctic
limit the cpu load of the build (either the amount of jobs, thus used cores: https://wiki.archlinux.org/title/Makepk … uild_times or w/ https://aur.archlinux.org/packages/cpulimit )
don't build houses out of hay, that's a really bad concept (there's a story about three little pigs explaining why)
why are you trying to build the package itfp? https://archlinux.org/packages/extra/x8 … itx5-mozc/
get a bigger fan
address the general heat issues of the system

I'm getting the packages off of the AUR, which then compiles itself, not the package you're referencing, which is on the extra repo.

How can I move it from the monolith to my "Mac"?

otherwise;

I can't move to the Arctic, that Mac will cause global warming to accelerate
limiting the CPU load will make it compile slower
I live in a apartment block mostly made out of concrete, and I am not a pig (not really kosher)
the Mac, being a Mac, has a tiny fan and there's nothing I can do about it (unless I put a desk fan in front of it, because Apple)
and the general heat issue of the system is that it probably just needs new thermal paste and I'm too lazy to open it up and spend time doing that

seth · 2024-06-22 16:09:47

I'm getting the packages off of the AUR, which then compiles itself

Why?

How can I move it from the monolith to my "Mac"?

Apple hasn't yet scrapped usb, have they? Otherwise nfs, smb, your google drive, some pastebin service, …

I live in a apartment block mostly made out of concrete

So it's the kind of concrete that the space witches used in Disneys latest StarWars imitation? Cause I've not seen other stones ever catching fire…

adr77 · 2024-06-22 16:16:31

seth wrote:

I'm getting the packages off of the AUR, which then compiles itself
Why?
How can I move it from the monolith to my "Mac"?
Apple hasn't yet scrapped usb, have they? Otherwise nfs, smb, your google drive, some pastebin service, …
I live in a apartment block mostly made out of concrete
So it's the kind of concrete that the space witches used in Disneys latest StarWars imitation? Cause I've not seen other stones ever catching fire…

the guide for Input methods suggest it.

by moving it, I mean on how can I make the package on the monolith, then move it to my Mac over USB.

(also noting, I didn't actually burn my house down with said Mac, it overheated mid-compilation to about 100*C and shut itself off. I have cleaned the only vent it has.)

seth · 2024-06-22 16:29:43

makepkg, https://wiki.archlinux.org/title/Aur

I can't make an informed statement about the different versions, but I'd probably give the one in the repo a try first.

I didn't actually burn my house down with said Mac, it overheated mid-compilation to about 100*C

Because you had read the story about the wold and the three little pigs and wisely decided to not to build your houe from hay

WorMzy · 2024-06-22 16:45:53

Mod note: moving to AUR Issues.

adr77 · 2024-06-22 16:58:48

seth wrote:

makepkg, https://wiki.archlinux.org/title/Aur
I can't make an informed statement about the different versions, but I'd probably give the one in the repo a try first.
I didn't actually burn my house down with said Mac, it overheated mid-compilation to about 100*C
Because you had read the story about the wold and the three little pigs and wisely decided to not to build your houe from hay

Trying to compile it, and it has one issue and I have one question; first off the issue:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/adr77/.cache/bazel/_bazel_adr77/0aa4192d183e9cc2e4224278d33620cd/server/jvm.out
Error: LinkageError occurred while loading main class com.google.devtools.build.lib.bazel.Bazel
        java.lang.UnsupportedClassVersionError: com/google/devtools/build/lib/bazel/Bazel has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 55.0
==> ERROR: A failure occurred in build().
    Aborting...

I run this command to begin everything:

makepkg -s

and the question is: where does it get put after compilation finishes?

seth · 2024-06-22 17:32:02

https://aur.archlinux.org/packages/fcit … ent-867172 ?
The package by default ends up in the same path as the PKGBUILD you're w/ makepkg (ie. the $PWD)

adr77 · 2024-06-22 17:58:54

seth wrote:

https://aur.archlinux.org/packages/fcit … ent-867172 ?
The package by default ends up in the same path as the PKGBUILD you're w/ makepkg (ie. the $PWD)

I've added the line

export CC='/usr/bin/gcc-13' export CXX='/usr/bin/g++-13'

to line 37 of the PKGBULID file, then added 2 blank lines (just pressed Enter twice). saved and it still fails.

current path of events:

[adr77@monolith fcitx5-mozc-ut]$ makepkg -s
==> Making package: fcitx5-mozc-ut 2.30.5490.102-2 (Sat 22 Jun 2024 20:51:41)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating fcitx5-mozc-ut-git git repo...
==> Validating source files with sha256sums...
    fcitx5-mozc-ut-git ... Passed
==> Extracting sources...
  -> Creating working copy of fcitx5-mozc-ut-git git repo...
Reset branch 'makepkg'
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/adr77/.cache/bazel/_bazel_adr77/0aa4192d183e9cc2e4224278d33620cd/server/jvm.out
Error: LinkageError occurred while loading main class com.google.devtools.build.lib.bazel.Bazel
        java.lang.UnsupportedClassVersionError: com/google/devtools/build/lib/bazel/Bazel has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 55.0
==> ERROR: A failure occurred in build().
    Aborting...

and a copy of my PKGBUILD file, maybe you'd be able to help out on that?

# Maintainer: Nocifer <apmichalopoulos at gmail dot com>
# Contributor: UTUMI Hirosi <utuhiro78 at yahoo dot co dot jp>
# Contributor: Felix Yan <felixonmars@gmail.com>
# Contributor: ponsfoot <cabezon dot hashimoto at gmail dot com>

pkgname='fcitx5-mozc-ut'
pkgver=2.30.5490.102
pkgrel=2
pkgdesc='Mozc module for Fcitx5'
arch=('x86_64')
url='https://github.com/fcitx/mozc'
license=('Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND GPL-2.0-or-later AND MIT AND NAIST-2003 AND Unicode-3.0 AND LicenseRef-Okinawa-Dictionary')
depends=('fcitx5' 'mozc>=2.30.5490.102')
makedepends=('bazel' 'git' 'python' 'qt6-base')
optdepends=('fcitx5-configtool')
provides=('fcitx5-mozc=2.30.5490.102')
conflicts=('fcitx5-mozc')
options=(!distcc !ccache)
source=("${pkgname}-git::git+https://github.com/fcitx/mozc.git#commit=8acc79f6e82dedaa5515da751fd7277e677ea02f")
sha256sums=('70920171e8ba52a555a13e6f6131ce01e182d45bb40462f515133af6162259c8')

prepare() {
    cd ${pkgname}-git/src

    git submodule update --init --recursive
}

build() {
    cd ${pkgname}-git/src

    unset ANDROID_NDK_HOME
    unset ANDROID_HOME
    export JAVA_HOME='/usr/lib/jvm/java-11-openjdk/'

    # Temp fix for GCC 14
    sed -i -e '/Werror/d' third_party/protobuf/build_defs/cpp_opts.bzl
    export CC='/usr/bin/gcc-13' export CXX='/usr/bin/g++-13

'
    bazel build unix/fcitx5:fcitx5-mozc.so unix/icons --config oss_linux --compilation_mode opt
}

package() {
    cd ${pkgname}-git/src

    # BSD-3-Clause
    sed -n 1,29p unix/fcitx5/fcitx_key_translator.h > Fcitx5
    sed -i -e 's|^\/\/[ ]\?||g' Fcitx5
    install -Dm644 Fcitx5 "${pkgdir}"/usr/share/licenses/${pkgname}/Fcitx5
    # BSD-3-Clause
    sed -n 67,94p data/installer/credits_en.html > Mozc
    install -Dm644 Mozc "${pkgdir}"/usr/share/licenses/${pkgname}/Mozc
    # BSD-3-Clause
    sed -n 317,344p data/installer/credits_en.html > Breakpad
    install -Dm644 Breakpad "${pkgdir}"/usr/share/licenses/${pkgname}/Breakpad
    # NAIST-2003
    sed -n 355,424p data/installer/credits_en.html > IPAdic
    install -Dm644 IPAdic "${pkgdir}"/usr/share/licenses/${pkgname}/IPAdic
    # BSD-2-Clause
    sed -n 435,457p data/installer/credits_en.html > Japanese-Usage-Dictionary
    install -Dm644 Japanese-Usage-Dictionary "${pkgdir}"/usr/share/licenses/${pkgname}/Japanese-Usage-Dictionary
    # Public Domain Data
    sed -n 468,470p data/installer/credits_en.html > Okinawa-Dictionary
    install -Dm644 Okinawa-Dictionary "${pkgdir}"/usr/share/licenses/${pkgname}/Okinawa-Dictionary
    # BSD-3-Clause
    sed -n 481,513p data/installer/credits_en.html > Protocol-Buffers
    install -Dm644 Protocol-Buffers "${pkgdir}"/usr/share/licenses/${pkgname}/Protocol-Buffers
    # MIT
    sed -n 698,704p data/installer/credits_en.html > Tamachi-Phonetic-Kanji-Alphabet
    install -Dm644 Tamachi-Phonetic-Kanji-Alphabet "${pkgdir}"/usr/share/licenses/${pkgname}/Tamachi-Phonetic-Kanji-Alphabet
    # MIT
    sed -n 762,782p data/installer/credits_en.html > Windows-Implementation-Library
    sed -i -e 's|^[ \t]*||g' Windows-Implementation-Library
    install -Dm644 Windows-Implementation-Library "${pkgdir}"/usr/share/licenses/${pkgname}/Windows-Implementation-Library

    install -Dm755 bazel-bin/unix/fcitx5/fcitx5-mozc.so "${pkgdir}"/usr/lib/fcitx5/fcitx5-mozc.so
    install -Dm644 unix/fcitx5/mozc-addon.conf "${pkgdir}"/usr/share/fcitx5/addon/mozc.conf
    install -Dm644 unix/fcitx5/mozc.conf "${pkgdir}"/usr/share/fcitx5/inputmethod/mozc.conf

    for pofile in unix/fcitx5/po/*.po
    do
        filename=`basename ${pofile}`
        lang=${filename/.po/}
        mofile=${pofile/.po/.mo}
        msgfmt ${pofile} -o ${mofile}
        install -Dm644 ${mofile} "${pkgdir}"/usr/share/locale/${lang}/LC_MESSAGES/fcitx5-mozc.mo
    done

    msgfmt --xml -d unix/fcitx5/po/ --template unix/fcitx5/org.fcitx.Fcitx5.Addon.Mozc.metainfo.xml.in -o unix/fcitx5/org.fcitx.Fcitx5.Addon.Mozc.metainfo.xml
    install -Dm644 unix/fcitx5/org.fcitx.Fcitx5.Addon.Mozc.metainfo.xml "${pkgdir}"/usr/share/metainfo/org.fcitx.Fcitx5.Addon.Mozc.metainfo.xml

    cd bazel-bin/unix

    unzip -o icons.zip

    install -Dm644 mozc.png                                     "${pkgdir}"/usr/share/icons/hicolor/128x128/apps/org.fcitx.Fcitx5.fcitx_mozc.png
    install -Dm644 alpha_full.svg                               "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_alpha_full.svg
    install -Dm644 alpha_half.svg                               "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_alpha_half.svg
    install -Dm644 direct.svg                                   "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_direct.svg
    install -Dm644 hiragana.svg                                 "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_hiragana.svg
    install -Dm644 katakana_full.svg                            "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_katakana_full.svg
    install -Dm644 katakana_half.svg                            "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_katakana_half.svg
    install -Dm644 outlined/dictionary.svg                      "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_dictionary.svg
    install -Dm644 outlined/properties.svg                      "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_properties.svg
    install -Dm644 outlined/tool.svg                            "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/org.fcitx.Fcitx5.fcitx_mozc_tool.svg

    ln -s org.fcitx.Fcitx5.fcitx_mozc.png                       "${pkgdir}"/usr/share/icons/hicolor/128x128/apps/fcitx_mozc.png
    ln -s org.fcitx.Fcitx5.fcitx_mozc_alpha_full.svg            "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_alpha_full.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_alpha_half.svg            "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_alpha_half.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_direct.svg                "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_direct.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_hiragana.svg              "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_hiragana.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_katakana_full.svg         "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_katakana_full.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_katakana_half.svg         "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_katakana_half.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_dictionary.svg            "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_dictionary.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_properties.svg            "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_properties.svg
    ln -s org.fcitx.Fcitx5.fcitx_mozc_tool.svg                  "${pkgdir}"/usr/share/icons/hicolor/scalable/apps/fcitx_mozc_tool.svg
}

seth · 2024-06-22 21:07:57

The link said

If you're getting compilation errors, please delete your Bazel cache (~/.cache/bazel by default).

Sounds relevant to your situation.

adr77 · 2024-06-22 21:18:57

seth wrote:

The link said
If you're getting compilation errors, please delete your Bazel cache (~/.cache/bazel by default).
Sounds relevant to your situation.

tried that, comes up with the same error.

seth · 2024-06-22 23:04:25

pacman -Qs java-environment

?

adr77 · 2024-06-22 23:08:19

seth wrote:

pacman -Qs java-environment

?

pulls this on the monolith

[adr77@monolith ~]$ pacman -Qs java-environment
local/java-environment-common 3-5
    Common files for Java Development Kits
local/jdk11-openjdk 11.0.23.u9-1
    OpenJDK Java 11 development kit
local/jdk21-openjdk 21.0.3.u9-1
    OpenJDK Java 21 development kit

and this pulls on the sevencommaone

[andaro@sevencommaone ~]$ pacman -Qs java-environment
local/java-environment-common 3-5
    Common files for Java Development Kits
local/jdk21-openjdk 21.0.3.u9-1
    OpenJDK Java 21 development kit

Last edited by adr77 (2024-06-22 23:10:15)

Scimmia · 2024-06-22 23:12:27

Which of those is default? See archlinux-java

seth · 2024-06-22 23:12:28

I'd say it picks up jdk11, https://wiki.archlinux.org/title/Java#S … etween_JVM

Edit: cross-talk

Last edited by seth (2024-06-22 23:13:19)

adr77 · 2024-06-22 23:26:15

so which one should I use to compile Mozc on the monolith with?

seth · 2024-06-23 06:11:53

Let's see, you've jdk11 and jdk21 and jdk11 is clearly wrong and jdk21 works on the macbook…
Hmmm… tough question. I don't really know ¯\_(ツ)_/¯

adr77 · 2024-06-23 06:43:20

seth wrote:

Let's see, you've jdk11 and jdk21 and jdk11 is clearly wrong and jdk21 works on the macbook…
Hmmm… tough question. I don't really know ¯\_(ツ)_/¯

I'm currently not home, but I have tried using it with jdk21, but reporting the same java error (my version doesn't match the version Bazel was compiled on.

seth · 2024-06-23 06:55:47

Tried "how"?

archlinux-java status

And make sure to clear the bazel cache.

adr77 · 2024-06-23 12:36:44

seth wrote:

Tried "how"?
archlinux-java status
And make sure to clear the bazel cache.

tried by using

sudo archlinux-java set java-21-openjdk

and cleared bazel's cache by running

rm -rf ~/.cache/bazel

then tried re-compiling but got this error:

[adr77@monolith fcitx5-mozc-ut]$ makepkg -s
==> Making package: fcitx5-mozc-ut 2.30.5490.102-2 (Sun 23 Jun 2024 15:35:32)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating fcitx5-mozc-ut-git git repo...
==> Validating source files with sha256sums...
    fcitx5-mozc-ut-git ... Passed
==> Extracting sources...
  -> Creating working copy of fcitx5-mozc-ut-git git repo...
Reset branch 'makepkg'
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/adr77/.cache/bazel/_bazel_adr77/e42118c8555b9325114a647baced22e4/server/jvm.out
Error: LinkageError occurred while loading main class com.google.devtools.build.lib.bazel.Bazel
        java.lang.UnsupportedClassVersionError: com/google/devtools/build/lib/bazel/Bazel has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 55.0
==> ERROR: A failure occurred in build().
    Aborting...

Is there a newer version of Java that needs to be present or is it just a compilation thing?

seth · 2024-06-23 12:56:34

Does the compilation actually work on the macbook (time demands aside)?
You could try to just remove jdk11 if that thing somehow insists on picking the wrong version.

adr77 · 2024-06-23 12:59:44

seth wrote:

Does the compilation actually work on the macbook (time demands aside)?
You could try to just remove jdk11 if that thing somehow insists on picking the wrong version.

Last I tried (which was over yay), it was about 80% done before it kicked the bucket from reaching 100*C.

it usually works on my other Arch devices, the monolith has done a full install in about 10 minutes with compilation, and my 13th gen. i7 starrybook took about 20 minutes.

I'll try compiling on the macbook again, but with a fan sitting in-front of it going full blast. I'll be back in a while for an update.

update: I have set a list of things that I had done before compilation began:

put away anything flammable at a reasonable distance
removed the additional casing it had (simple thing made from plastic, decorative reasons only)
plugged it into the wall
put the fan in-front of the Mac, and will put it on full blast once compilation starts

16:11:50 IDT: currently cloning some stuff... will update later once compilation starts, not looking good so far...

Last edited by adr77 (2024-06-23 13:12:32)

seth · 2024-06-23 13:16:02

The only question is whether it also bails w/ a java/bazel error.
If not, try to remove jdk11 from the monolith so the build cannot use it.

Just as a reminder: have you tried the repo package and found it insufficient for your needs?

adr77 · 2024-06-23 13:19:42

seth wrote:

The only question is whether it also bails w/ a java/bazel error.
If not, try to remove jdk11 from the monolith so the build cannot use it.
Just as a reminder: have you tried the repo package and found it insufficient for your needs?

the repo package seems to be out of date, and it doesn't seem to be the same as the AUR version.

It's still cloning stuff on the Mac, mostly failing because of my slow internet.

update: failed again, gonna do this:

uninstall JDK 11 from monolith
try and compile
if still fails, gonna put it to the side for the time being, Japanese input isn't as important to me as English or Hebrew, which work fine for the time under Fcitx5.

update 2: can't figure out what is the name for JDK 11's package name so I could remove it. Help please? used pacman -Qs java and found it.

update 3: it works. currently compiling on monolith. I. AM. SHOOKETH.

update 4: making mozc for the Mac, as it needs it as a dependency. overall, smooth sailing so far.

Last edited by adr77 (2024-06-23 13:43:55)

Arch Linux

#1 2024-06-22 00:18:25

Installing Mozc on my MacBook without it burning down [SOLVED]

#2 2024-06-22 06:21:53

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#3 2024-06-22 11:10:25

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#4 2024-06-22 16:09:47

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#5 2024-06-22 16:16:31

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#6 2024-06-22 16:29:43

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#7 2024-06-22 16:45:53

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#8 2024-06-22 16:58:48

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#9 2024-06-22 17:32:02

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#10 2024-06-22 17:58:54

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#11 2024-06-22 21:07:57

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#12 2024-06-22 21:18:57

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#13 2024-06-22 23:04:25

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#14 2024-06-22 23:08:19

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#15 2024-06-22 23:12:27

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#16 2024-06-22 23:12:28

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#17 2024-06-22 23:26:15

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#18 2024-06-23 06:11:53

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#19 2024-06-23 06:43:20

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#20 2024-06-23 06:55:47

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#21 2024-06-23 12:36:44

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#22 2024-06-23 12:56:34

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#23 2024-06-23 12:59:44

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#24 2024-06-23 13:16:02

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

#25 2024-06-23 13:19:42

Re: Installing Mozc on my MacBook without it burning down [SOLVED]

Board footer