~firasuke

Aleppo, Syria

A radiologist who's a Linux developer that loves arm wrestling and is interested in 中文


#108 basu fails to build with muon 3 months ago

Comment by ~firasuke on ~lattis/muon

Just faced the exact same issue with glib. This appears to be a problem with the to_int() method with null terminated strings.

#108 basu fails to build with muon 3 months ago

Ticket created by ~firasuke on ~lattis/muon

Hey there, I am trying to build basu using muon on a custom Linux distribution that uses musl libc. I am receiving the following error:

basu-v0.2.1/meson.build:208:47: error unable to parse '65534\10'
208 |                 id = id_result.stdout().to_int()
                                                    ^
basu-v0.2.1/meson.build:208:41: error in method str.to_int()
208 |                 id = id_result.stdout().to_int()

I tried it with meson and it builds just fine, which lead me to believe it's a muon bug.

Any ideas?

https://todo.sr.ht/~emersion/basu/19

#19 Unable to parse '65534\10` 3 months ago

Ticket created by ~firasuke on ~emersion/basu

Hey there, I am trying to build basu using muon on a custom Linux distribution that uses musl libc. I am receiving the following error:

basu-v0.2.1/meson.build:208:47: error unable to parse '65534\10'
208 |                 id = id_result.stdout().to_int()
                                                    ^
basu-v0.2.1/meson.build:208:41: error in method str.to_int()
208 |                 id = id_result.stdout().to_int()

I tried it with meson and it builds just fine, which lead me to believe it's a muon bug.

Any ideas that it might be caused by basu?

#107 Support for --cross-file 3 months ago

Ticket created by ~firasuke on ~lattis/muon

I am trying to cross compile muon to a musl libc target, using muon on a glibc host. It is detecting the cross compiler correctly having passed it via PATH and CC, but it is failing on tools/embedder file.

This works for meson as I have a cross-file listing all binaries from ar, as all the way to strings and strip.

I checked muon's source code and noticed that --cross-file is ignored, so is there a way to solve this?

#98 Support building in remote out-of-tree directories 10 months ago

Comment by ~firasuke on ~lattis/muon

I can confirm that relative paths are now working. I even tried the bootstrap script with relative paths, and it worked as expected in all trials.

Keep up the great work!

#98 Support building in remote out-of-tree directories 10 months ago

on ~lattis/muon

~firasuke, did you test the latest master? It should now work even with .. in the path.

#98 Support building in remote out-of-tree directories 10 months ago

Comment by ~firasuke on ~lattis/muon

Thanks for your input on this.

I can confirm this only happens when using a relative path "../build_dir" or when using an absolute path with relative elements "$PWD/../build_dir" (as if path resolution is not getting picked up?)..

It works fine when I specify "/some/path/to/build_dir" with no relative elements whatsoever.

#98 Support building in remote out-of-tree directories 10 months ago

Comment by ~firasuke on ~lattis/muon

I apologize if I didn't make myself clear.

I am not asking whether muon/meson are run from within the source directory or not. I understand that you have to be inside the source directory to run muon/meson.

But what I don't understand is why should the build directory be inside the source directory as well?

Why does this work with meson:

cd source_dir
meson setup ../build_dir
samu -C ../build_dir
samu -C ../build_dir install

and this does not work with muon?

cd source_dir
muon setup ../build_dir
samu -C ../build_dir // samu fails due to missing meson_options.txt or other files

Also why should I install with "muon -C ../build_dir install" when using muon, instead of running "samu -C ../build_dir install" like meson?

#98 Support building in remote out-of-tree directories 10 months ago

Comment by ~firasuke on ~lattis/muon

"muon -C builddir setup" works whether builddir is in tree or out of tree, but "samu -C builddir" only works in tree.

This is not an issue with "samu" because when using "meson", samu just works fine and in and out of tree.

#98 Support building in remote out-of-tree directories 10 months ago

Ticket created by ~firasuke on ~lattis/muon

As mentioned in the title, with "meson" I generally create an out-of-tree build directory where "meson -C /path/to/build/directory setup" is run, then "samu -C /path/to/build/directory" is run, followed by "samu -C /path/to/build/directory install", but with "muon" I am able to run "muon -C /path/to/build/directory setup" but running "samu" next does not work as it does not see meson_options.txt? Also why do we have to use "muon -C /path/to/build/directory install" to install something instead of "samu"?