#30

uh oh. libuv error came back when I ran CFLAGS=-Wno-address-ofpacked-member ./waf

heres the output: http://ix.io/1WCk

Do we know why it wasnt avoided here?

#31

did you pass CFLAGS at configure stage? also what’s the output of ./waf -v?

#32

I believe I’ve passed CFLAGS at configure. I interpreting this as I ran CFLAGS=-Wno-address-ofpacked-member ./waf configure and then this was the output: http://ix.io/1WUm. Correct me if I’ve miss understood what you mean by pass CFLAGS.

Heres the output of ./waf -v is: http://ix.io/1WUB

#33

Ah, sorry, my mistake above. Notice, that the flag is passed to the compiler:

image
image691×267 27.5 KB

But there’s a typo, should be -Wno-address-of-packed-member, can you try it with a dash?

#34

please can you type the exact command, that you mean?

#35 
CFLAGS=-Wno-address-of-packed-member ./waf configure
./waf
#36

ah sorry see. cool. Configure went fine so did ./waf.
Heres the output for ./waf install: http://ix.io/1WX2

#37

Like I mentioned above, you should only do waf install if you want a system-wide install for some reason, but I won’t recommend this if you’re not sure what you’re doing. Try running it locally as described above and see if it work fine first.

#38

okay the monomes plugged in this is the responce from ./build/bin/serialoscd: http://ix.io/1X1M

because Im running it locally is there a problem reaching libmonome?

#39

It’s unrelated to running locally, but there clearly is some problem with your libmonome install, unfortunately I don’t know how yay installs packages, so can’t be of much help here. Was it installed without errors?

#40

no errors but so im not alone I’ll download libmonome from: https://github.com/monome/libmonome and report what it says next. Its hard to document yay’s results

#41

i’ve downloaded https://github.com/monome/libmonome.
heres the result of ./waf configure: http://ix.io/1XE7
…and the result of ./waf: http://ix.io/1XHa

got the same error still from running serialoscd.

I guess its a case now of installing ftdi_sio and usbserial…
also Im not yet clear what you meant yet by “Don’t forget to replace debian-specific package install instructions with arch-specific”

#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