> Many parts of C11 including optional features are not supported by libc.
Are you referring to glibc? If so, C11 atomics should also work on OS/2? > And some feature test macros such as __STDC_NO_THREADS__ are not defined by gcc. Hm, I guess you meant they ARE defined, else this would be surprisingly good news. Anyway, that's good to know so far, thanks. Tom 2017-10-13 16:07 GMT+02:00 KO Myung-Hun <k...@chollian.net>: > > Many parts of C11 including optional features are not supported by libc. > And some feature test macros such as __STDC_NO_THREADS__ are not defined by > gcc. In case of C++11, I could build many projects using C++11 without > problems. However, there are missing wide-character functions such as > vwprintf(). > > --------------- Original message ------------- > > From : "Tom M."<tom.m...@googlemail.com> > To : "FluidSynth mailing list"<fluid-dev@nongnu.org> > CC : > Date : Fri, 13 Oct 2017 0:52:51 +0900 (KST), Thu, 12 Oct 2017 17:52:06 > +0200 > > Subject : Re: [fluid-dev] I removed GLIB dependency from my build. > > Are C11 or C++11 programs compilable on OS/2 or ArcaOS? > > > Tom > > 2017-10-12 16:24 GMT+02:00 KO Myung-Hun <k...@chollian.net>: > >> Hi/2. >> >> OS/2 is still alive. ^^ And, OS/2 is being sold as ArcaOS by Arca Noae( >> https://www.arcanoae.com/). >> >> --------------- Original message ------------- >> >> From : "Philippe Simons"<simons.phili...@gmail.com> >> To : "FluidSynth mailing list"<fluid-dev@nongnu.org> >> CC : >> Date : Thu, 12 Oct 2017 1:4:44 +0900 (KST), Wed, 11 Oct 2017 18:00:43 >> +0200 >> Subject : Re: [fluid-dev] I removed GLIB dependency from my build. >> >> Isn't OS/2 already dead anyway? >> >> On Wed, Oct 11, 2017 at 10:19 AM, Tom M. <tom.m...@googlemail.com> wrote: >> >>> TinyCThread looks good. Even though they only support Win32 and Pthreads >>> they implement the C11 API. So we could move to C11: >>> >>> #ifdef __STDC_NO_ATOMICS__ >>> #error "Compiler has no C11 atomics" >>> #endif >>> >>> #ifdef __STDC_NO_THREADS__ >>> #include <tinycthread.h> >>> #else >>> #include <threads.h> >>> #endif >>> >>> This however might be the end of OS/2 support. Compiling on Win32 only >>> with MinGW or CygWin. Would this really make the Windows users life easier >>> as originally intended by the glib removal? >>> >>> >>> Tom >>> >>> >>> 2017-10-10 23:54 GMT+02:00 Ryan Gonzalez <rym...@gmail.com>: >>> >>>> FWIW I had been working on removing glib two years ago or a bit less >>>> (dang, was it really that long ago?), as this is basically why I >>>> stopped when I was almost done: it really wasn't maintainable. >>>> >>>> Realistically, I do think there's literally no major alternative. I >>>> mean, for atomics there's libatomic_ops: >>>> >>>> https://github.com/ivmai/libatomic_ops >>>> >>>> which was built for and is still used by the Boehm GC. If Windows is >>>> the only barrier to C11 adoption, maybe TinyCThread could fill in for >>>> the mean time? https://tinycthread.github.io/ >>>> >>>> On Tue, Oct 10, 2017 at 12:25 PM, Tom M. <tom.m...@googlemail.com> >>>> wrote: >>>> > Without having seen your changes, you have probably done something >>>> like what >>>> > existed before glib: >>>> > https://github.com/FluidSynth/fluidsynth/blob/ >>>> b49458e817ed09aedd948a6ea1831965373adc80/fluidsynth/src/ >>>> fluid_sys.h#L142 >>>> > >>>> > This is not an option because it's unmaintainable. See the related >>>> > discussion here for possible solutions: >>>> > http://lists.nongnu.org/archive/html/fluid-dev/2017-09/msg00031.html >>>> > >>>> > >>>> > Tom >>>> > >>>> > >>>> > 2017-10-10 18:57 GMT+02:00 Carlo Bramini <carlo.bra...@libero.it>: >>>> >> >>>> >> Hello, >>>> >> as I wrote in the subject, I worked a bit on Fluidsynth and I made a >>>> >> version that works fine without external dependencies. I compiled it >>>> on the >>>> >> ancient VisualStudio 6.0 and my version currentl runs on Windows. >>>> >> However, it should not be difficult to include a new driver for >>>> adding >>>> >> again support to GLIB at compile time or to add support for other >>>> platforms, >>>> >> especially direct pthreads support. >>>> >> I'm wondering if you would be interested to evaluate these changes >>>> and how >>>> >> to do it if it could be possible to add them to the original source >>>> code. >>>> >> I have still some work to do on it, because some functions are still >>>> not >>>> >> implemented and my coding started almost from version 1.1.7 (I >>>> cloned the >>>> >> repository a bit before the release of the latest stable) but in the >>>> >> meanwhile new patches have been submitted, so I should also align my >>>> code at >>>> >> latest revision. >>>> >> >>>> >> Sincerely. >>>> >> >>>> >> _______________________________________________ >>>> >> fluid-dev mailing list >>>> >> fluid-dev@nongnu.org >>>> >> https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > fluid-dev mailing list >>>> > fluid-dev@nongnu.org >>>> > https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>> > >>>> >>>> -- >>>> Ryan (ライアン) >>>> Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else >>>> https://refi64.com/ >>>> >>>> _______________________________________________ >>>> fluid-dev mailing list >>>> fluid-dev@nongnu.org >>>> https://lists.nongnu.org/mailman/listinfo/fluid-dev >>>> >>> >>> _______________________________________________ >>> fluid-dev mailing list >>> fluid-dev@nongnu.org >>> https://lists.nongnu.org/mailman/listinfo/fluid-dev >> >> >> _______________________________________________ >> fluid-dev mailing list >> fluid-dev@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/fluid-dev >> > > > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev > >
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
