search

oeai / m-audio-usb-midi-fw

M-Audio USB MIDI Firmware Loaders for Linux
Other
14 stars 3 forks source link

does not recognize udev version 244.3-1 as greater then 128 #3

Open calacuda opened 4 years ago

calacuda commented 4 years ago

when I try to run ./config I get this output.

hecking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for fxload... /usr/sbin/fxload
checking for udev version... ./configure: line 1738: /sbin/udevadm: No such file or directory
none
configure: error: udev version 128 or later is required
oeai commented 4 years ago

sorry i don't remember already this project, i had some slight changes here you can see files "first copy" and you can press on "udev changes" to see what was changed then try to debug https://github.com/oeai/m-audio-usb-midi-fw/commit/8ba9d01d555b41e673139a83b91a6003a411bea5 you can try to build for some not so much modern kernel seems like udevadm system somehow changed for example they've changed the name of "udevadm" program, so all you need is to change the "udevadm" name to something new in whole project

if it will work for you, then you can fork this project, make your changes and publish for all

Some-E commented 4 years ago

I've just used this successfully. On Ubuntu 18 (I think, if it was not older and then upgraded) I could use the original from SourceForge, but not in 19. So I found this and had problems (biggest was a typo in filename, already requested pull of my fork). I think I also removed the path from the fxload command in the rules, but I cannot remember the udev version check, did I just comment it out or what. I'm writing this because I've just fiddled and learned a lot because things didn't go smoothly - and I could possibly help others with what I've learned.

grammoboy2 commented 3 years ago

I've a issue too on Debian testing:

m-audio-usb-midi-fw$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for fxload... /sbin/fxload checking for udev version... ./configure: line 1740: /sbin/udevadm: No such file or directory none configure: error: udev version 128 or later is required

oeai commented 3 years ago

so the udev version check is in ./configure -script line 1740 @grammoboy2 can you make some changes there and check it? you need to find how udevadm is called in system now and change it there

grammoboy2 commented 3 years ago

$ locate udevadm /usr/bin/udevadm /usr/lib/systemd/system/initrd-udevadm-cleanup-db.service /usr/share/bash-completion/completions/_udevadm /usr/share/bash-completion/completions/udevadm /usr/share/lintian/tags/u/udevadm-called-without-guard.tag /usr/share/man/man8/udevadm.8.gz /usr/share/zsh/vendor-completions/_udevadm

grammoboy2 commented 3 years ago

m-audio-usb-midi-fw$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for fxload... /sbin/fxload checking for udev version... 247 checking for /etc/udev/udev.conf... yes checking for udev rules directory... not found; assuming /etc/udev/rules.d configure: creating ./config.status config.status: creating Makefile config.status: WARNING: 'Makefile.in' seems to ignore the --datarootdir setting

grammoboy2 commented 3 years ago

I don't have it running yet, it builds, but not sure if it works configure.txt

oeai commented 3 years ago

it should work. thanks.

grammoboy2 commented 3 years ago

I changed the version to 148 I believe and /sbin/udevadm to /usr/bin/udevadm

But I don't feel like I know what I'm doing...

oeai commented 3 years ago

I changed the version to 148 I believe and /sbin/udevadm to /usr/bin/udevadm

that is just what is needed, maybe in other distros they are using /sbin for udevadm maybe it should be in a different version of code for it, but probably it will be alright for most users, who needs that. and they can find this issue too.