digitalmars.D.ldc - LDC 1.1.0-beta6
- kinke (32/32) Dec 13 2016 Hey all,
- Soulsbane (9/41) Dec 14 2016 I have a problem when compiling a project that uses LuaD. I don't
- kink (4/12) Dec 14 2016 Looks as if the Lua C library isn't passed to the linker. Please
- Soulsbane (4/9) Dec 14 2016 Ok, for some reason dmd worked just fine without having liblua5.1
- Mike Parker (3/6) Dec 15 2016 That's because of this line in LuaD's dub.json:
- Mike Parker (3/9) Dec 15 2016 And this one:
- Guillaume Piolat (4/13) Dec 27 2016 I've started testing this release, but it would be easier if it
- Guillaume Piolat (3/6) Dec 27 2016 Found it, the right name is "ldc-1.1.0-beta6"
- Dicebot (1/1) Jan 02 2017 Waiting for 1.1.0 final very very much ;)
- Dan Olson (8/13) Jan 04 2017 I spent some time catching up on D and tried this 1.1.0-beta6 version on
Hey all, on behalf of the LDC team I am proud to announce the new 1.1.0-beta6 release! It's based on the 2.071.2 frontend and standard library and supports LLVM 3.5 up to current trunk (4.0). Beta 6 is what beta 4 should have been, but early testing revealed some issues (thanks for reporting!) before official announcements were made, so we're at beta 6 now and looking forward to a final release, depending on your feedback! The highlights of this release are Link-Time Optimization, DLL exports on Windows and, as always, a multitude of bugfixes. This time, we only provide binaries for Linux, OS X and Windows; the usual FreeBSD and Linux/ARM (armv7hf) ones are missing due to limited manpower. Changelog and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.1.0-beta6 All binaries are built with LLVM 3.9. * The Linux x86/x86_64 binaries are built on Ubuntu 12.04 LTS and work on Ubuntu 12.04 LTS (or later) without installing additional software. * The OS X binaries are built on OS X 10.10 and require at least OS X 10.8. * The Windows binaries are built on Windows 10 with Visual Studio 2015 (update 3). They require a VS2015 or Visual C++ Build Tools installation for linking (and depend on the Visual C++ 2015 runtime). The 64-bit package is a multilib one capable of targeting x86 via `-m32`. Please be sure to report any bugs at https://github.com/ldc-developers/ldc/issues. Thanks to everybody involved in making this happen! Regards, kinke
Dec 13 2016
On Tuesday, 13 December 2016 at 19:52:40 UTC, kinke wrote:Hey all, on behalf of the LDC team I am proud to announce the new 1.1.0-beta6 release! It's based on the 2.071.2 frontend and standard library and supports LLVM 3.5 up to current trunk (4.0). Beta 6 is what beta 4 should have been, but early testing revealed some issues (thanks for reporting!) before official announcements were made, so we're at beta 6 now and looking forward to a final release, depending on your feedback! The highlights of this release are Link-Time Optimization, DLL exports on Windows and, as always, a multitude of bugfixes. This time, we only provide binaries for Linux, OS X and Windows; the usual FreeBSD and Linux/ARM (armv7hf) ones are missing due to limited manpower. Changelog and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.1.0-beta6 All binaries are built with LLVM 3.9. * The Linux x86/x86_64 binaries are built on Ubuntu 12.04 LTS and work on Ubuntu 12.04 LTS (or later) without installing additional software. * The OS X binaries are built on OS X 10.10 and require at least OS X 10.8. * The Windows binaries are built on Windows 10 with Visual Studio 2015 (update 3). They require a VS2015 or Visual C++ Build Tools installation for linking (and depend on the Visual C++ 2015 runtime). The 64-bit package is a multilib one capable of targeting x86 via `-m32`. Please be sure to report any bugs at https://github.com/ldc-developers/ldc/issues. Thanks to everybody involved in making this happen! Regards, kinkeI have a problem when compiling a project that uses LuaD. I don't see any issues reported yet on LuaD's github so I'm not sure where the problem originates. Anyway I get this when linking: ../../../.dub/packages/luad-master/luad/.dub/build/library-release-linux.posix-x86_64-ldc_0-B1357DF9F0EC274CDA75A2B3B084BCDA/libl ad.a(luad.state.o): In function `_D4luad5state8LuaState8openLibsMFNeZv': ../../../.dub/packages/luad-master/luad/luad/state.d:(.text._D4luad5state8LuaState8openLibsMFNeZv[_D4luad5state8LuaState8o enLibsMFNeZv]+0xf): undefined reference to `luaL_openlibs' collect2: error: ld returned 1 exit status Everything works fine with DMD though.
Dec 14 2016
On Wednesday, 14 December 2016 at 09:28:23 UTC, Soulsbane wrote:I have a problem when compiling a project that uses LuaD. I don't see any issues reported yet on LuaD's github so I'm not sure where the problem originates. Anyway I get this when linking: ../../../.dub/packages/luad-master/luad/.dub/build/library-release-linux.posix-x86_64-ldc_0-B1357DF9F0EC274CDA75A2B3B084BCDA/libl ad.a(luad.state.o): In function `_D4luad5state8LuaState8openLibsMFNeZv': ../../../.dub/packages/luad-master/luad/luad/state.d:(.text._D4luad5state8LuaState8openLibsMFNeZv[_D4luad5state8LuaState8o enLibsMFNeZv]+0xf): undefined reference to `luaL_openlibs' collect2: error: ld returned 1 exit status Everything works fine with DMD though.Looks as if the Lua C library isn't passed to the linker. Please check the command lines to figure out where the difference comes from and then raise an issue.
Dec 14 2016
On Wednesday, 14 December 2016 at 11:34:21 UTC, kink wrote:On Wednesday, 14 December 2016 at 09:28:23 UTC, Soulsbane wrote:Ok, for some reason dmd worked just fine without having liblua5.1 in my dub.sdl and has for months. Anyway, fixed now though. Thanks.[...]Looks as if the Lua C library isn't passed to the linker. Please check the command lines to figure out where the difference comes from and then raise an issue.
Dec 14 2016
On Thursday, 15 December 2016 at 06:04:05 UTC, Soulsbane wrote:Ok, for some reason dmd worked just fine without having liblua5.1 in my dub.sdl and has for months. Anyway, fixed now though. Thanks.That's because of this line in LuaD's dub.json: "libs-windows-x86_64-dmd": ["lua5.1"],
Dec 15 2016
On Thursday, 15 December 2016 at 09:02:39 UTC, Mike Parker wrote:On Thursday, 15 December 2016 at 06:04:05 UTC, Soulsbane wrote:And this one: "sourceFiles-windows-x86-dmd": ["extlib/lua5.1.lib"],Ok, for some reason dmd worked just fine without having liblua5.1 in my dub.sdl and has for months. Anyway, fixed now though. Thanks.That's because of this line in LuaD's dub.json: "libs-windows-x86_64-dmd": ["lua5.1"],
Dec 15 2016
On Thursday, 15 December 2016 at 09:03:33 UTC, Mike Parker wrote:On Thursday, 15 December 2016 at 09:02:39 UTC, Mike Parker wrote:yeah, I saw that but I'm on Linux. Anyway all is good. Thanks.On Thursday, 15 December 2016 at 06:04:05 UTC, Soulsbane wrote:And this one: "sourceFiles-windows-x86-dmd": ["extlib/lua5.1.lib"],Ok, for some reason dmd worked just fine without having liblua5.1 in my dub.sdl and has for months. Anyway, fixed now though. Thanks.That's because of this line in LuaD's dub.json: "libs-windows-x86_64-dmd": ["lua5.1"],
Dec 15 2016
kinke <noone nowhere.com> On Thursday, 15 December 2016 at 22:40:59 UTC, Soulsbane wrote:On Thursday, 15 December 2016 at 09:03:33 UTC, Mike Parker wrote:So if the following lines in dub.json ``` "sourceFiles-linux-x86": ["extlib/x86_32-linux-gnu/liblua.a"], "sourceFiles-linux-x86_64": ["extlib/x86_64-linux-gnu/liblua.a"], ``` don't work with LDC but do with DMD, please file a DUB issue about it, in order to save others from this annoyance.On Thursday, 15 December 2016 at 09:02:39 UTC, Mike Parker wrote:yeah, I saw that but I'm on Linux. Anyway all is good. Thanks.On Thursday, 15 December 2016 at 06:04:05 UTC, Soulsbane wrote:And this one: "sourceFiles-windows-x86-dmd": ["extlib/lua5.1.lib"],Ok, for some reason dmd worked just fine without having liblua5.1 in my dub.sdl and has for months. Anyway, fixed now though. Thanks.That's because of this line in LuaD's dub.json: "libs-windows-x86_64-dmd": ["lua5.1"],
Dec 16 2016
On Tuesday, 13 December 2016 at 19:52:40 UTC, kinke wrote:Hey all, on behalf of the LDC team I am proud to announce the new 1.1.0-beta6 release! It's based on the 2.071.2 frontend and standard library and supports LLVM 3.5 up to current trunk (4.0). Beta 6 is what beta 4 should have been, but early testing revealed some issues (thanks for reporting!) before official announcements were made, so we're at beta 6 now and looking forward to a final release, depending on your feedback!I've started testing this release, but it would be easier if it was available on Travis CI. Have I missed something? I've tried "ldc-1.1.0-b6"
Dec 27 2016
On Wednesday, 28 December 2016 at 00:17:11 UTC, Guillaume Piolat wrote:I've started testing this release, but it would be easier if it was available on Travis CI. Have I missed something? I've tried "ldc-1.1.0-b6"Found it, the right name is "ldc-1.1.0-beta6"
Dec 27 2016
kinke <noone nowhere.com> writes:Hey all, on behalf of the LDC team I am proud to announce the new 1.1.0-beta6 release! It's based on the 2.071.2 frontend and standard library and supports LLVM 3.5 up to current trunk (4.0).I spent some time catching up on D and tried this 1.1.0-beta6 version on Rasperry Pi 3 with LLVM 3.9.1. The dmd-testsuite is getting Bus Errors in 4 tests. I haven't dug in to investigate yet. Anybody know the last tagged version that passed dmd-testsuite on ARMv7? -- Dan
Jan 04 2017
Hey Dan, good to see you back. On Wednesday, 4 January 2017 at 14:40:18 UTC, Dan Olson wrote:kinke <noone nowhere.com> writes:The dmd tests ran fine for me natively on Android/ARM as of ed22ff1 from master, dunno about tagged versions. Could it be specific to armhf?Hey all, on behalf of the LDC team I am proud to announce the new 1.1.0-beta6 release! It's based on the 2.071.2 frontend and standard library and supports LLVM 3.5 up to current trunk (4.0).I spent some time catching up on D and tried this 1.1.0-beta6 version on Rasperry Pi 3 with LLVM 3.9.1. The dmd-testsuite is getting Bus Errors in 4 tests. I haven't dug in to investigate yet. Anybody know the last tagged version that passed dmd-testsuite on ARMv7?
Jan 04 2017
Joakim <dlang joakim.fea.st> writes:Hey Dan, good to see you back.Thanks!On Wednesday, 4 January 2017 at 14:40:18 UTC, Dan Olson wrote: The dmd tests ran fine for me natively on Android/ARM as of ed22ff1 from master, dunno about tagged versions. Could it be specific to armhf?I tried making ed22ff1 and make errors out when linking ldc. Some duplicate druntime symbols. So going backwards... Built 1.1.0-beta3 and that is golden with dmd-testsuite except for lit tests which I don't think have ever been made ARM-ready. I guess next is finding the commit that introduced Bus Errors sometime after beta3 before tackling the linker problem. gdb shows all cases happen in code generated for synchronized blocks, something messed up in D_CRITICAL_SECTION, probably the pthread_mutex_t.
Jan 05 2017
Dan Olson <gorox comcast.net> writes:Joakim <dlang joakim.fea.st> writes:Introduced in commit 8d06f23 "Allow align(1) for global variables". I'll have to study it, but my guess is that there was an existing alignment problem and this commit just revealed it. Added https://github.com/ldc-developers/ldc/issues/1955Hey Dan, good to see you back.Thanks!On Wednesday, 4 January 2017 at 14:40:18 UTC, Dan Olson wrote: The dmd tests ran fine for me natively on Android/ARM as of ed22ff1 from master, dunno about tagged versions. Could it be specific to armhf?I tried making ed22ff1 and make errors out when linking ldc. Some duplicate druntime symbols. So going backwards... Built 1.1.0-beta3 and that is golden with dmd-testsuite except for lit tests which I don't think have ever been made ARM-ready. I guess next is finding the commit that introduced Bus Errors sometime after beta3 before tackling the linker problem. gdb shows all cases happen in code generated for synchronized blocks, something messed up in D_CRITICAL_SECTION, probably the pthread_mutex_t.
Jan 06 2017