[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #9 from Jon Kleiser --- (In reply to Seb from comment #8) > Hmm could it be that this is due to your installation as it looks like your > linking with a different standard library than your source include paths > have. > How did you install D and could you check that DMD is using them correct > standard library? > You can see the imports and linker commands when compiling with -v (e.g. > hello world). I installed using the installer, first dmd.2.085.0.dmg, then dmd.2.085.1.dmg. The same on three different Macs. --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #8 from Seb --- Hmm could it be that this is due to your installation as it looks like your linking with a different standard library than your source include paths have. How did you install D and could you check that DMD is using them correct standard library? You can see the imports and linker commands when compiling with -v (e.g. hello world). --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #7 from Jon Kleiser --- (In reply to Seb from comment #6) > Did you clone the vibe.d repository and go into the examples/websocket > directory to run the websocket example or where did you get it from? I have now cloned the vibe.d repo. The vibe.d/examples/websocket did build and run w/o problems. I also tried to dub build the vibe.d/examples/http_server, but that ended like this: http-server-example ~master: building configuration "application"... Linking... Undefined symbols for architecture x86_64: "__D6object__T10RTInfoImplVAmA2i104i1322ZQBbyG2m", referenced from: __D85TypeInfo_S4vibe4core4path__T11GenericPathTSQBhQBfQBd17WindowsPathFormatZQBs9PathRange6__initZ in http-server-example.o "__D6object__T10RTInfoImplVAmA2i224i33ZQzyG2m", referenced from: __D229TypeInfo_S9eventcore7drivers12threadedfile__T23ThreadedFileEventDriverHTCQClQCe5posix6even -- lots more - ntDriverHTCQClQCe5posix6events__T22PosixEventDriverEventsHTCQEiQEbQBx6kqueue15KqueueEventLoopHTCQFsQFlQDh7sockets__T23PosixEventDriverSocketsHTQDgZQBfZQEoZQGq__T7taskFunVAyaa4_72656164ThZQBaFNbNiNfCQJqQJjQJe__TQItHTQHxZQJcSQKp6driver6FileFDmAhZvTQBxTQBcTmTQpZQMh6__initZ in http-server-example.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Error: linker exited with status 1 /Library/D/dmd/bin/dmd failed with exit code 1. --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #6 from Seb --- Did you clone the vibe.d repository and go into the examples/websocket directory to run the websocket example or where did you get it from? --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #5 from Jon Kleiser --- (In reply to Jon Kleiser from comment #4) > (In reply to Seb from comment #3) > > Hmm, did this error occur when trying to build the websocket example from > > the Vibe.d source tree. What version of Vibe.d do you build? > > I tried both 0.8.5 and 0.8.6-alpha.1. I may have misunderstood your question re. the Vibe.d source tree. I also did try the tiny hello.d (Hello Vibe.d) at code.dlang.org/packages/vibe-d. It ran, and was listening and responding on 8080, in spite of the yellow text in the log saying "Failed to listen on 0.0.0.0:8080". --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #4 from Jon Kleiser --- (In reply to Seb from comment #3) > Hmm, did this error occur when trying to build the websocket example from > the Vibe.d source tree. What version of Vibe.d do you build? I tried both 0.8.5 and 0.8.6-alpha.1. --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #3 from Seb --- Hmm, did this error occur when trying to build the websocket example from the Vibe.d source tree. What version of Vibe.d do you build? --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 --- Comment #2 from Jon Kleiser --- It may be so. The reason I thought it was more general, is I get a somewhat similar error when trying to build the websocket demo code found here: https://wiki.dlang.org/User:Csmith1991/Vibe.d_Documentation/websocket This is what I get: websocket_chat ~master: building configuration "application"... Linking... Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable (maybe you meant: __d_main_args, __D4core6thread6Thread7sm_mainCQBcQBaQw , __D4core6thread16_mainThreadStoreG312v ) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Error: linker exited with status 1 /Library/D/dmd/bin/dmd failed with exit code 1. --
[Issue 19801] Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 Seb changed: What|Removed |Added CC||greeen...@gmail.com --- Comment #1 from Seb --- That's probably an issue with drepl. Please report there. Thanks! --
[Issue 15371] __traits(getMember) should bypass the protection
https://issues.dlang.org/show_bug.cgi?id=15371 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #9 from Dlang Bot --- @RazvanN7 created dlang/dmd pull request #9585 "Fix Issue 15371 - __traits(getMember) should bypass the protection" fixing this issue: - Fix Issue 15371 - __traits(getMember) should bypass the protection https://github.com/dlang/dmd/pull/9585 --
[Issue 19724] Regression: wrong order of linker arguments, again: -L-l before -L--start-group
https://issues.dlang.org/show_bug.cgi?id=19724 --- Comment #3 from Dlang Bot --- dlang/dmd pull request #9582 "For issue 19724, group library files explicitly listed with `-L=` in with other library-related `-L=` flags." was merged into master: - a4f755520bda18f8b944760fe4d7ca98dad63b88 by Mathis Beer: For issue 19724, group library files explicitly listed with `-L=` in with other library-related `-L=` flags. https://github.com/dlang/dmd/pull/9582 --
[Issue 19801] New: Linking error: ld: symbol(s) not found for architecture x86_64
https://issues.dlang.org/show_bug.cgi?id=19801 Issue ID: 19801 Summary: Linking error: ld: symbol(s) not found for architecture x86_64 Product: D Version: D2 Hardware: x86 OS: Mac OS X Status: NEW Severity: blocker Priority: P1 Component: tools Assignee: nob...@puremagic.com Reporter: jon.klei...@icloud.com I try to install the D REPL. After having done "dub fetch drepl" successfully, I do "dub run drepl". That job ends like this: drepl 0.2.1: building configuration "console"... Running pre-build commands... Linking... Undefined symbols for architecture x86_64: "__D6object__T10RTInfoImplVAmA2i48i60Z4datayG2m", referenced from: __D42TypeInfo_S3std7variant__T8VariantNVmi32ZQp6__initZ in libstdx-allocator.a(concurrency_103_72a.o) "__D6object__T10RTInfoImplVAmA2i80i961Z4datayG2m", referenced from: __D59TypeInfo_S3std11concurrency__T4ListTSQBbQBa7MessageZQw4Node6__initZ in libstdx-allocator.a(atomic_ef_466.o) "_rt_loadLibrary", referenced from: __D4core7runtime7Runtime__T11loadLibraryZQoFxAaZPv in drepl.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Error: linker exited with status 1 /Library/D/dmd/bin/dmd failed with exit code 1. I have tried with both DMD64 D Compiler v2.085.0 and v2.085.1. I'm running macOS 10.14.4 (the latest). --
[Issue 19800] New: JSON output does not include scoped imports
https://issues.dlang.org/show_bug.cgi?id=19800
Issue ID: 19800
Summary: JSON output does not include scoped imports
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P1
Component: dmd
Assignee: nob...@puremagic.com
Reporter: goalit...@dissues.mail.kapsi.fi
The JSON output generated by -X does not include modules imported within
functions:
void main()
{
import std.stdio;
writeln("hi");
}
Compiled and run with following command:
dmd -Xf- -run main.d
run.dlang.io link to same snippet of code: https://run.dlang.io/is/C91HBX
JSON output:
[
{
"kind" : "module",
"file" : "onlineapp.d",
"members" : [
{
"name" : "main",
"kind" : "function",
"line" : 1,
"char" : 6,
"deco" : "FZv",
"endline" : 5,
"endchar" : 1
}
]
}
]
--
[Issue 19799] templated string formatting fails with const Nullable!string
https://issues.dlang.org/show_bug.cgi?id=19799 FeepingCreature changed: What|Removed |Added Severity|enhancement |major --
[Issue 19799] templated string formatting fails with const Nullable!string
https://issues.dlang.org/show_bug.cgi?id=19799 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @FeepingCreature created dlang/phobos pull request #6954 "Fix issue 19799: add const toString to Nullable" fixing this issue: - Fix issue 19799: add const toString to Nullable to avoid miscompilation in Nullable!string due to attempted implicit .get conversion to string https://github.com/dlang/phobos/pull/6954 --
[Issue 19799] New: templated string formatting fails with const Nullable!string
https://issues.dlang.org/show_bug.cgi?id=19799
Issue ID: 19799
Summary: templated string formatting fails with const
Nullable!string
Product: D
Version: D2
Hardware: x86_64
OS: Linux
Status: NEW
Severity: enhancement
Priority: P1
Component: phobos
Assignee: nob...@puremagic.com
Reporter: default_357-l...@yahoo.de
import std.stdio;
import std.typecons;
void main() { writefln!"%s"(const(Nullable!string)()); }
--
Expected: "Nullable.null"
Got: horrible format template barf.
Come on guys. This code is too simple to fail so badly.
--
