Note on dependency arch for Fedora

[frantisekhanzlikbl]

Bevy version

0.4.0

Operating system & version

Fedora 33

What you did

1. follow the Linux dependency setup for Fedora 33
2. cargo init --bin
3. add the Bevy dependency
4. add some code from any of the "getting started" tutorial sections
5. try to build the project

What you expected to happen

The project should build successfully

What actually happened

The build failed with confusing linker errors.

the relevant part of build log

  = note: /usr/bin/ld: skipping incompatible /usr/lib/libasound.so when searching for -lasound
          /usr/bin/ld: skipping incompatible /usr/lib/libasound.so when searching for -lasound
          /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-redhat-linux/10/../../../libasound.so when searching for -lasound
          /usr/bin/ld: skipping incompatible /lib/libasound.so when searching for -lasound
          /usr/bin/ld: skipping incompatible /usr/lib/libasound.so when searching for -lasound
          /usr/bin/ld: cannot find -lasound

Additional information

This was caused by alsa-lib-devel.i686 being installed on my system from the past, probably for building some other project.
Unfortunately, DNF does not issue any warning if I attempt to install alsa-lib-devel without explicitly specifying the arch, while already having the package installed for a non-default arch and instead just exits with a message about the package already being installed.

This is not directly a Bevy bug, but it was very confusing for someone not familiar with the linking process and not used to building a lot of software from source. It would be very helpful to add this somewhere in the (Fedora?) (not sure if this only affects DNF or other package managers as well) deps section, as it was very unclear why did ld not see the so in /usr/lib64/alsa.so and I have spent a lot of time tweaking the linker args instead of focusing on the real issue.

Also note that the solution was as simple as doing # dnf install alsa-lib-devel.x86_64