daemonize.cpp:483:13: error: 'sched_yield' was not declared in this scope

[thegdyne]

hi there, got the following when i tried to make

daemonize.cpp: In function 'bool seq64::microsleep(int)':
daemonize.cpp:483:13: error: 'sched_yield' was not declared in this scope
483 | sched_yield();
| ^~~~~~~~~~~
make[2]: *** [Makefile:729: daemonize.lo] Error 1

#history was as follows
727 libtoolize
728 automake --add-missing
729 ./configure --enable-release --enable-rtmidi
730 make

Please can you help? thanks

[ahlstromcj]

I will check it out soon. What distro are you using? You can also try the Seq66 project. It's more up to date than Seq64 and does a lot more!

On Fri, Feb 17, 2023 at 18:40 thegdyne ***@***.***> wrote: hi there, got the following when i tried to make daemonize.cpp: In function 'bool seq64::microsleep(int)': daemonize.cpp:483:13: error: 'sched_yield' was not declared in this scope 483 | sched_yield(); | ^~~~~~~~~~~ make[2]: *** [Makefile:729: daemonize.lo] Error 1 #history was as follows 727 libtoolize 728 automake --add-missing 729 ./configure --enable-release --enable-rtmidi 730 make Please can you help? thanks — Reply to this email directly, view it on GitHub <#222>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB45LKEN5UGLUHW3K5FKWE3WYAEATANCNFSM6AAAAAAU77LZFI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Chris Ahlstrom

[thegdyne]

Thanks bro using fedora 36 will check seq66 appreciate your reply

…

On Sat, 18 Feb 2023, 15:54 C. Ahlstrom, ***@***.***> wrote: I will check it out soon. What distro are you using? You can also try the Seq66 project. It's more up to date than Seq64 and does a lot more! On Fri, Feb 17, 2023 at 18:40 thegdyne ***@***.***> wrote: > hi there, got the following when i tried to make > > daemonize.cpp: In function 'bool seq64::microsleep(int)': > daemonize.cpp:483:13: error: 'sched_yield' was not declared in this scope > 483 | sched_yield(); > | ^~~~~~~~~~~ > make[2]: *** [Makefile:729: daemonize.lo] Error 1 > > #history was as follows > 727 libtoolize > 728 automake --add-missing > 729 ./configure --enable-release --enable-rtmidi > 730 make > > Please can you help? thanks > > — > Reply to this email directly, view it on GitHub > <#222>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AB45LKEN5UGLUHW3K5FKWE3WYAEATANCNFSM6AAAAAAU77LZFI > > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- Chris Ahlstrom — Reply to this email directly, view it on GitHub <#222 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4A4XIA6TKMGGANPDYJNADWYDWDNANCNFSM6AAAAAAU77LZFI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[thegdyne]

Succeeded in getting seq66 running...thanks very much!!

…

On Sat, 18 Feb 2023, 15:54 C. Ahlstrom, ***@***.***> wrote: I will check it out soon. What distro are you using? You can also try the Seq66 project. It's more up to date than Seq64 and does a lot more! On Fri, Feb 17, 2023 at 18:40 thegdyne ***@***.***> wrote: > hi there, got the following when i tried to make > > daemonize.cpp: In function 'bool seq64::microsleep(int)': > daemonize.cpp:483:13: error: 'sched_yield' was not declared in this scope > 483 | sched_yield(); > | ^~~~~~~~~~~ > make[2]: *** [Makefile:729: daemonize.lo] Error 1 > > #history was as follows > 727 libtoolize > 728 automake --add-missing > 729 ./configure --enable-release --enable-rtmidi > 730 make > > Please can you help? thanks > > — > Reply to this email directly, view it on GitHub > <#222>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AB45LKEN5UGLUHW3K5FKWE3WYAEATANCNFSM6AAAAAAU77LZFI > > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- Chris Ahlstrom — Reply to this email directly, view it on GitHub <#222 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4A4XIA6TKMGGANPDYJNADWYDWDNANCNFSM6AAAAAAU77LZFI> . You are receiving this because you authored the thread.Message ID: ***@***.***>