#42

I don’t think there are any issues with the drivers.

Serialosc build instructions for raspbian include Debian-specific commands to run, make sure you understand how to go through same steps in Arch Linux - it’s not a distro for newbies, so maybe you can ask for help on Arch-specific resources as well.

Running ./waf in libmonome will only build it inside the source directory, ./waf install will install it, but I don’t recommend it again, because your manually compiled version will likely cause conflicts with the arch package sooner or later.

#43

Okay so it looks like we’ve installed serialosc and libmonome would you agree from the results you’ve seen?

…So, there are Debian specific commands included in the Raspian build instructions. And your suggesting I find those commands and then find equivalent commands for arch Linux?

Friendly Side NOTE: That’s confusing its not like the setup instructions for arch Linux explain to refer to the Raspian set up find the Debian steps and run the equivalent steps in arch :D?

Its not clear to me what the Debian specific steps are? May you point them out please? And I can go ahead and find the arch equivalent.

I was guessing its the step with the command on because it has the word “deb” in there:
echo “deb http://ppa.launchpad.net/artfwo/monome/ubuntu bionic main” | sudo tee /etc/apt/sources.list.d/monome.list

also what are we expecting to happen after we do this?

#44

I might be missing something but aren’t there packages in the AUR for serialosc (https://aur.archlinux.org/packages/serialosc-git/) and libmonome (https://aur.archlinux.org/packages/libmonome-git/)?
Why are you trying to build and install these packages yourself outside of your package manager?

If there’s something wrong with those packages then I’d suggest to start with the existing PKGBUILD, try to fix it, use makepkg (https://wiki.archlinux.org/index.php/Makepkg) to build and if it works suggest the fix to the package maintainer in a comment (or maybe a PR? I don’t know if that’s possible).

#45

I think the previous few post should answer your initial question.

i think @artfwo might be more of there expert here to fully explain the whys.

Personally, i will note what you mentioned and attempt that at a later stage. It don’t think its as quicker solution at this moment in time for me. I’d rather not drop the progress thats been made over the last couple of days…

#46

I’m definitely not an expert here. I’m not even using arch linux, just trying to help with my limited knowledge :slight_smile:

Fixing the packages, as @simonvanderveldt suggested would be of course the best option, maybe modifying PKGBUILD to ignore no-address-of-packed-member build error.

1 Like
#47

aha sorry @artfwo…may I get your take on my last post referring to the Debien steps and carrying out equivalent arch linux steps

#48

@simonvanderveldt in response to your post here.

Just to confirm what I should perhaps attempt…

Shalll I download load https://aur.archlinux.org/packages/serialosc-git/ and https://aur.archlinux.org/packages/libmonome-git/ by running git clone?

Inside the serialosc and libmonome git folders there will be the PKGBUILD file. And I can attempt to correct the PKGBUILD. In this case as @artfwo suggested, maybe finding the correct point use no-address-of-packed-member.

Ill report back on my progress :S

#49

Yeah, that sounds about right, probably enough to just add the CFLAGS to this line https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=serialosc-git#n23 for example.

1 Like
#50

which line are you specifying here?

May I get your take on this PKGBUILD file ill attempt to run: http://ix.io/21Re

Is the CFLAGS in the correct place to we reckon?
Is there anything else I need to consider?
EDIT: ive ran that PKGBUILD looks like serialosc has successfully installed heres the result: http://ix.io/21Rj

in the meantime libmonome looks good i think. I’ve run the comand makepkg -si and this is the output: http://ix.io/21Rh

2ndEDIT: i have to run serialoscd as root but the compiler says: serialosc [m0001026]: connected , server running on port 15882

:slight_smile: I think this means its working ! :smiley:

So i should try let the package maintainer know now ay :slight_smile:

#51

PKGBUILD looks good to me.

Looking at the output of makepkg I think you’ll need to add the -f (or --force) flag to make it actually (re)build the package, it currently seems to be using an old build.

From the makepkg man page

-f, --force

makepkg will not build a package if a built package already exists in the PKGDEST (set in makepkg.conf(5)) directory, which may default to the current directory. This allows the built package to be overwritten.

(I don’t use Arch myself, so this could be wrong, but it seems like the obvious thing to try)

1 Like
#52

ah, I think that build is there from only moments before. I was just trying to recreate the output. But the -f flag is good to know

1 Like
#53

I was just going by these lines:

==> WARNING: A package has already been built, installing existing package...
==> Installing package libmonome-git with pacman -U...
warning: libmonome-git-20190608-1 is up to date -- reinstalling

which sounds like it’s reusing a build from before, and it’s mentioning 20190608 which seems like some time ago (and doesn’t match the PKGBUILD version) so I’m assuming it’s using the already built package from that date.

But like I said I don’t use Arch so could be wrong :slight_smile:

1 Like
#54

is this function simply missing from the latest python version? how can I correct that?

#55

You were using Python 3.6 before?
async became a reserved keyword in 3.7, see https://docs.python.org/3/whatsnew/3.7.html#summary-release-highlights

#56

Right, this is faders example from pymonome, I’ve updated it for python3.7 syntax now too: https://github.com/artfwo/pymonome/blob/master/examples/faders.py

#57

Okay so. Do I need to uninstall python 3.8.0 (which is what I have currently) and Install python3.7 instead, perhaps using this link? : https://aur.archlinux.org/packages/python37/

#58

No, should work with python 3.8 too, have you tried running the updated example?

1 Like