Package Details: solfege 3.23.4-11

Git Clone URL: https://aur.archlinux.org/solfege.git (read-only, click to copy)
Package Base: solfege
Description: Music education and ear training software
Upstream URL: https://www.gnu.org/software/solfege/
Licenses: GPL-3.0-only
Groups: pro-audio
Submitter: gromit
Maintainer: lquidfire
Last Packager: lquidfire
Votes: 2
Popularity: 0.89
First Submitted: 2024-03-19 23:20 (UTC)
Last Updated: 2024-07-03 12:45 (UTC)

Dependencies (22)

Required by (0)

Sources (9)

Latest Comments

Alf2010 commented on 2024-07-05 18:06 (UTC)

Hi @lquidfire and @PS0, the compil is OK. Thank's !!!

lquidfire commented on 2024-07-03 10:28 (UTC)

Thank you for the find, PS0! Same conclusion as reached on the forums by V1del. This works and a new version will be uploaded soon.

PS0 commented on 2024-07-03 07:44 (UTC)

Removing the search path of /usr/src/linux in the soundcard makefile will fix the issue.

sed -e '26s/ -I\/usr\/src\/linux\/include//' -i "solfege/soundcard/Makefile"

lquidfire commented on 2024-07-02 11:50 (UTC)

Great catch, @PS0!

I have started a thread on the bbs! https://bbs.archlinux.org/viewtopic.php?pid=2181344

PS0 commented on 2024-07-02 09:41 (UTC)

It seems that the clean chroot build only uses the linux api headers, whereas the 'dirty' build also uses the kernel headers of the installed kernel (/usr/src/linux).

lquidfire commented on 2024-07-01 13:50 (UTC)

Hi @Tiagofer and @Alf2010, could you please post about this in the forums, with a full compile log? I cannot reproduce this which makes it a bit hard to debug. Thank you!

Alf2010 commented on 2024-06-30 15:12 (UTC)

Hi Lquidfire I have the same problem than Tiagofer. I didn't change anything in my build environment and I can build other aur packages with no problem. My message is just for info because I don't use this software for a long time, it is just installed and complained during update... Thank's for your work

lquidfire commented on 2024-06-26 12:50 (UTC)

Hi @Tiagofer,

I can build solfege in a clean chroot. Did you change anything about your build environment?

What if you stop those issues being treated as errors by gcc 14?

Tiagofer commented on 2024-06-26 08:47 (UTC)

I'm getting the following errors when compiling:

In file included from /usr/src/linux/include/linux/swab.h:5,
                 from /usr/src/linux/include/uapi/linux/byteorder/little_endian.h:14,
                 from /usr/src/linux/include/linux/byteorder/little_endian.h:5,
                 from /usr/include/asm/byteorder.h:5,
                 from /usr/src/linux/include/linux/soundcard.h:27,
                 from /usr/include/sys/soundcard.h:1,
                 from solfege/soundcard/macro_to_function.c:22:
/usr/src/linux/include/uapi/linux/swab.h:48:15: error: unknown type name ‘__attribute_const__’; did you mean ‘__attribute__’?
   48 | static inline __attribute_const__ __u16 __fswab16(__u16 val)
      |               ^~~~~~~~~~~~~~~~~~~
      |               __attribute__
/usr/src/linux/include/uapi/linux/swab.h:48:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__fswab16’
   48 | static inline __attribute_const__ __u16 __fswab16(__u16 val)
      |                                         ^~~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h:57:15: error: unknown type name ‘__attribute_const__’; did you mean ‘__attribute__’?
   57 | static inline __attribute_const__ __u32 __fswab32(__u32 val)
      |               ^~~~~~~~~~~~~~~~~~~
      |               __attribute__
/usr/src/linux/include/uapi/linux/swab.h:57:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__fswab32’
   57 | static inline __attribute_const__ __u32 __fswab32(__u32 val)
      |                                         ^~~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h:66:15: error: unknown type name ‘__attribute_const__’; did you mean ‘__attribute__’?
   66 | static inline __attribute_const__ __u64 __fswab64(__u64 val)
      |               ^~~~~~~~~~~~~~~~~~~
      |               __attribute__
/usr/src/linux/include/uapi/linux/swab.h:66:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__fswab64’
   66 | static inline __attribute_const__ __u64 __fswab64(__u64 val)
      |                                         ^~~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h:79:15: error: unknown type name ‘__attribute_const__’; did you mean ‘__attribute__’?
   79 | static inline __attribute_const__ __u32 __fswahw32(__u32 val)
      |               ^~~~~~~~~~~~~~~~~~~
      |               __attribute__
/usr/src/linux/include/uapi/linux/swab.h:79:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__fs
wahw32’
   79 | static inline __attribute_const__ __u32 __fswahw32(__u32 val)
      |                                         ^~~~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h:88:15: error: unknown type name ‘__attribute_const__’; did you mean ‘__attribute__’?
   88 | static inline __attribute_const__ __u32 __fswahb32(__u32 val)
      |               ^~~~~~~~~~~~~~~~~~~
      |               __attribute__
/usr/src/linux/include/uapi/linux/swab.h:88:41: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__fswahb32’
   88 | static inline __attribute_const__ __u32 __fswahb32(__u32 val)
      |                                         ^~~~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h: In function ‘__swab’:
/usr/src/linux/include/uapi/linux/swab.h:139:16: error: implicit declaration of function ‘__fswab64’; did you mean ‘__swab’? [-Wimplicit-function-declaration]
  139 |         return __swab64(y);
      |                ^~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h: In function ‘__swab16p’:
/usr/src/linux/include/uapi/linux/swab.h:176:16: error: implicit declaration of function ‘__fswab16’; did you mean ‘__swab16p’? [-Wimplicit-function-declaration]
  176 |         return __swab16(*p);
      |                ^~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h: In function ‘__swab32p’:
/usr/src/linux/include/uapi/linux/swab.h:189:16: error: implicit declaration of function ‘__fswab32’; did you mean ‘__swab32p’? [-Wimplicit-function-declaration]
  189 |         return __swab32(*p);
      |                ^~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h: In function ‘__swahw32p’:
/usr/src/linux/include/uapi/linux/swab.h:217:16: error: implicit declaration of function ‘__fswahw32’; did you mean ‘__swahw32p’? [-Wimplicit-function-declaration]
  217 |         return __swahw32(*p);
      |                ^~~~~~~~~
/usr/src/linux/include/uapi/linux/swab.h: In function ‘__swahb32p’:
/usr/src/linux/include/uapi/linux/swab.h:232:16: error: implicit declaration of function ‘__fswahb32’; did you mean ‘__swahb32p’? [-Wimplicit-function-declaration]
  232 |         return __swahb32(*p);
      |                ^~~~~~~~~
make[1]: *** [<builtin>: solfege/soundcard/macro_to_function.o] Error 1