From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 753716 for gnuports@2rosenthals.com; Mon, 11 May 2020 00:52:30 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:45062 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1jY0QP-0007zQ-0F for gnuports@2rosenthals.com; Mon, 11 May 2020 00:52:21 -0400 Received: from elasmtp-dupuy.atl.sa.earthlink.net ([209.86.89.62]:33924) by mail2.2rosenthals.com with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1jY0QI-00066D-2D for gnuports@2rosenthals.com; Mon, 11 May 2020 00:52:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1589172734; bh=MFvDb6RW46YAVShlBfr6Lih0at8evhZnlJcF xinzmH8=; h=Received:From:Date:To:In-Reply-To:Subject:X-Mailer: Message-ID:X-ELNK-Trace:X-Originating-IP; b=Ul4KgT4g6Hvm8oPqmF6wS8 I7rQUUu2wTM6Fo2TVcwaqEA5hmITkCU2ieq8aTlROODGfZ1A0URs2Z4l8WUgvgW0/1q 3rDk/xz0AhT1Jp65mu+yy3qxlhaLH4OFsmzlMjZAoO1fOwW4N5JtiYeX5jf6x0AmHiv FIv3Os/DRY1qINT/9CvkaKkkUX9RRUWJldgnuRzRQTNgYlBws6vFYkr7Ur4Qzp/6sTZ QTlihayiN+IWfgGqMxv5FW9mF7ksBsm4tU202w0+0qjCC10BWBydpy/Ti3xJlFSkjw1 tNlYk3bMqBqQM/xKa0vkSg3iTY3UpSf7qVSeJRL4bE3igMxyTz2g== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=GKTRipbbWSs9J35sg92CJ3SDW5vM2r13inpdID60bGbQ1jcv0+ThE0fr5Jz1jlFQrx4ImIyF+dbwpvPzTnCo0c45r5ClhNxBbV1KtHv12EkFB0fyArWsxkF92uvDoTz83UmB5pmHodGW2uQIfYG7K7zk9jDZO+HWHKU21n5Crj+bhZgVoH2bDt1kxitSmokYhCCMntepCUtCe0qAqi83gH8EVdm68/jtc2bwYdXGWTNoioP0W+z2vkWkS1V2cRXaHIDQ9ca7kvR7CxSIiXIZQ0eWV29Ppv2Xv3tYzWMQyZW8X6Vr4SlSdzRVHvgA1ANnuOJ4nI8UyhZQ66o213lr+w==; h=Received:From:Date:To:In-Reply-To:Subject:X-Mailer:Message-ID:X-ELNK-Trace:X-Originating-IP; Received: from [108.193.254.132] (helo=slamain) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from ) id 1jY0Pi-000Aqt-Tj for gnuports@2rosenthals.com; Mon, 11 May 2020 00:51:39 -0400 Date: Sun, 10 May 2020 21:21:41 -0700 To: "GNU Ports for eCS Mailing List" In-Reply-To: Subject: Re: [GNU Ports] _beginthread not declared X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.21 BETA/60 Message-ID: X-ELNK-Trace: a1109158fca87577d780f4a490ca6956846b590522b13c95913583432b6974c1e3dbc94fcc6cce9a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 108.193.254.132 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable In , on 05/10/20 at 02:15 PM, "Dave Yeo" said: Hi Dave, >I thought of that, but I can't find them in the source excepting=20 >_POSIX_SOURCE which is in CMakeLists.txt in an EMSCRIPTEN block. Since=20 >emscription is a toolchain to build asm.js/WebAssembly, I doubt that it=20 >is getting defined. I know what cmake is, but I've never used cmake myself. However I am somewhat buzzword compliant after a quick google for cmake tutorial I quickly learned that CMakeLists.txt is what the cmake folks decided to name their makefiles. I am sure they had their reasons. It is trival for you to check if it is getting defined. No guessing is required. Add the following to one of your source files: #if defined(_POSIX_SOURCE) #error I am defined #endif >This is my first visit to a CMake build and I have no idea how to do=20 >simple things like make V=3D1 to get a more informative build and there=20 >seems to be one makefile which makes adding stuff like -E hard. https://cliutils.gitlab.io/modern-cmake/chapters/features/debug.html describes som edebugging techniques. https://stackoverflow.com/questions/10085945/set-cflags-and-cxxflags-opti= ons-using-cmake seems to explain how to add values to CFLAGS My current take is that cmake is much like kbuild with different syntax. >I did >follow Paul's suggestion and added the definition of _beginthread which >fixed the issue. That's a good interim solution. >Where log2 is wrapped in a __USE_GNU block and defining that before=20 >including math.h didn't help, You always fix it the same way you fixed _beginthread. This will work just fine as long as log2 is implemented and it appears that it is implemented by kLIBC. >It's >frustrating these defines guarding common functions and these are not >the type of fixes to send upstream. These guards may be specific to our gcc port. Do the same guards appear in the pristine gcc sources. From what I've seen investigating your _beginlibpath, they do not. I doubt there are any fixes to be sent upsteam to the gcc maintainers.=20 It's possible that tickets need to be submitted the bww gcc issues tracker to bring our includes more in sync with what the gcc maintainers consider current standards. Steven --=20 ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ---------------------------------------------------------------------- --=20 This email was Anti Virus checked by Astaro Security Gateway. http://www.so= phos.com