x27;m at a loss for how to fix this linker error. Any help would
be appreciated.
You may have to specify the OpenSSL version with vibe-stream:tls
https://vibed.org/docs#http-https
-Steve
Thanks. I added the following to my dub.sdl file:
```
dependency "vibe-stream:tls" version=&quo
On Tuesday, 10 September 2024 at 20:41:12 UTC, Curtis Spencer
wrote:
I'm attempting to upgrade the vibe-d dependencies of a project.
The project compiles fine using `dub`, but the linker fails
with:
…
I'm at a loss for how to fix this linker error. Any help would
be appreciated.
REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
$ apt list --installed | grep libssl
libssl-dev/noble-updates,noble-security,now 3.0.13-0ubuntu3.4
amd64 [installed]
libssl3t64/noble-updates,noble-security,now 3.0.13-0ubuntu3.4
amd64 [installed,automatic]
```
I'm at a loss for how to fix this linker error. Any help would be
appreciated.
On Saturday, 8 June 2024 at 02:22:00 UTC, Xiaochao Yan wrote:
Hi, I am new to D and is experimenting with game development
using D and C.
I had some problem when trying to recreate the
https://dlang.org/spec/importc.html
[...]
Thanks in advance!
on a recent compiler this should work:
```d
On Saturday, 8 June 2024 at 02:22:00 UTC, Xiaochao Yan wrote:
Hi, I am new to D and is experimenting with game development
using D and C.
I had some problem when trying to recreate the
https://dlang.org/spec/importc.html
Environment:
Windows 11
gcc.exe (i686-posix-dwarf-rev0, Built by MinGW-W6
Hi, I am new to D and is experimenting with game development
using D and C.
I had some problem when trying to recreate the
https://dlang.org/spec/importc.html
Environment:
Windows 11
gcc.exe (i686-posix-dwarf-rev0, Built by MinGW-W64 project) 8.1.0
Error Message:
```
lld-link: error: undefined
On 7/9/23 10:01 AM, Dmitry Olshansky wrote:
Trying to compile the following:
https://github.com/DmitryOlshansky/photon/blob/master/tests/curl_download.d
with:
ldc2 curl_download.d -L-lcurl
get:
"__D6photon12__ModuleInfoZ", referenced from:
__D13curl_download12__ModuleInfoZ in curl_d
Trying to compile the following:
https://github.com/DmitryOlshansky/photon/blob/master/tests/curl_download.d
with:
ldc2 curl_download.d -L-lcurl
get:
"__D6photon12__ModuleInfoZ", referenced from:
__D13curl_download12__ModuleInfoZ in curl_download.o
"__D6photon5macos4core2goFDFZvZv",
On Saturday, 1 October 2022 at 21:18:05 UTC, Ali Çehreli wrote:
On 10/1/22 11:15, Kyle Ingraham wrote:
> storing structs as
> `void*` in a wrapper struct with information about their
module and
> identifier saved elsewhere.
Perhaps unrelated but that part reminded me of the following
discussio
On 10/1/22 11:15, Kyle Ingraham wrote:
> storing structs as
> `void*` in a wrapper struct with information about their module and
> identifier saved elsewhere.
Perhaps unrelated but that part reminded me of the following discussion:
https://forum.dlang.org/post/tfbn10$19nv$1...@digitalmars.co
On Tuesday, 13 September 2022 at 08:43:45 UTC, Nick Treleaven
wrote:
On Tuesday, 13 September 2022 at 03:00:17 UTC, Kyle Ingraham
wrote:
Any suggestions for being able to call one function for any
instance given but maintain flexible return types?
Not sure if it helps, but you can define final
On Tuesday, 13 September 2022 at 03:00:17 UTC, Kyle Ingraham
wrote:
Any suggestions for being able to call one function for any
instance given but maintain flexible return types?
Not sure if it helps, but you can define final methods in an
interface, which can call virtual interface methods:
#limitations
Templates cannot be used to add non-static fields or virtual
functions to classes or interfaces.
You *should* get an error from the compiler for trying to do
this, instead of just a linker error somewhere else down the
line, but either way it's not going to work. You'll hav
functions to classes or interfaces.
You *should* get an error from the compiler for trying to do
this, instead of just a linker error somewhere else down the
line, but either way it's not going to work. You'll have to find
another solution.
I am writing a library where I would like to be able to store
instances of a type of class to an associative array for later
usage. Each class stored has to implement a function as part of
the required interface. The argument given is always the same
type but the return value should be flexible
On Wednesday, 1 June 2022 at 15:23:14 UTC, Kagamin wrote:
Try to run clang with -v option and compare with gcc.
I've tracked down the problem to the solution where i specify as
linker to use gcc12 instead of a clang/llvm.
The following works.
```
export CC=clang14
ldc2 --link-defaultlib-share
On Wednesday, 3 August 2022 at 09:39:36 UTC, ryuukk_ wrote:
Does adding ```-m64``` work
I'm using macOS so I don't think that applies. But no, it doesn't
do anything for me.
Thanks,
--anonymouse
Does adding ```-m64``` work
On Wednesday, 3 August 2022 at 05:04:08 UTC, H. S. Teoh wrote:
On Wed, Aug 03, 2022 at 04:28:57AM +, anonymouse via
Digitalmars-d-learn wrote:
How do I go about tracking down what's causing the following
error:
```
Undefined symbols for architecture x86_64:
"__D3std8internal6memory12__Mo
On Wed, Aug 03, 2022 at 04:28:57AM +, anonymouse via Digitalmars-d-learn
wrote:
> How do I go about tracking down what's causing the following error:
>
> ```
> Undefined symbols for architecture x86_64:
> "__D3std8internal6memory12__ModuleInfoZ", referenced from:
> __D3loxQe12__Module
How do I go about tracking down what's causing the following
error:
```
Undefined symbols for architecture x86_64:
"__D3std8internal6memory12__ModuleInfoZ", referenced from:
__D3loxQe12__ModuleInfoZ in dlux.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command fa
Try to run clang with -v option and compare with gcc.
The detailed error is :
```
/usr/bin/clang test.o -o test -L/usr/local/lib -lphobos2-ldc
-ldruntime-ldc -Wl,--gc-sections -lexecinfo -lpthread -lm -m64
ld: error: undefined hidden symbol: __start___minfo
referenced by test.d
test.o:(ldc.register_dso)
```
Performed additional tests.
Compiling helloworld.d
```
export CC=gcc11 ; ldc2 helloworld.d
```
works fine.
Compiling helloworld.d
```
export CC=clang ; ldc2 helloworld.d
```
returns:
```
d: error: undefined hidden symbol: __start___minfo
referenced by test.d
test.o:(ldc.register_ds
Bugs in the clang/llvm toolchain but not in the gcc toolchain ?
The following worked , and i don't know what is going on:
```
ldc2 --gcc=gcc11
```
The problem re-appeared and i have totally no idea what caused it.
ldc2 test.d
ld: error: undefined hidden symbol: __start___minfo
referenced by test.d
test.o:(ldc.register_dso)
ld: error: undefined hidden symbol: __stop___minfo
referenced by test.d
test.o:(ldc.regi
On 18/03/2022 5:56 PM, rikki cattermole wrote:
Are you trying to build dub on Android?
Android support for ldc is currently broken to due to removal of a
linker that is currently required for TLS support.
https://github.com/ldc-developers/ldc/issues/3918
My bad I didn't see FreeBSD.
Simi
Are you trying to build dub on Android?
Android support for ldc is currently broken to due to removal of a
linker that is currently required for TLS support.
https://github.com/ldc-developers/ldc/issues/3918
I disabled 32bit code maybe this created the following error
while building dub :
[00:02:18]
===
[00:02:18] ===>
[00:02:18] ===> Configuring for dub-1.14.0
[00:02:23]
=
Most of the time these are dependency-issues. You need to install
a package called python-dev. This package includes header files,
a static library and development tools for building Python
modules, extending the Python interpreter or embedding Python in
applications. When encountering this err
On Tuesday, 12 October 2021 at 00:01:25 UTC, jfondren wrote:
On Monday, 11 October 2021 at 23:43:17 UTC, Ruby The Roobster
wrote:
package mixin template move__() {
pragma(inline) package void mv(Point moveby, ref Skeleton
tomove) {
foreach(i;tomove.faces) {
On Monday, 11 October 2021 at 23:43:17 UTC, Ruby The Roobster
wrote:
package mixin template move__() {
pragma(inline) package void mv(Point moveby, ref Skeleton
tomove) {
foreach(i;tomove.faces) {
foreach(k;i.lines) {
So, I have the following two files:
skeleton.d:
```d
/*skeleton.d by Ruby The Roobster*/
/*Version 1.0 Release*/
/*Module for representing skeletons in the D Programming Language
2.0*/
/*This program is free software: you can redistribute it and/or
modify
it under the terms of the GNU General P
On Wednesday, 4 August 2021 at 01:10:15 UTC, Mike Parker wrote:
On Tuesday, 3 August 2021 at 21:40:09 UTC, james.p.leblanc
wrote:
[...]
The alias to Complex!double is a template instantiation. A
template instantiation creates a symbol that needs to be
linked. So you need to compile my_module
On Tuesday, 3 August 2021 at 21:40:09 UTC, james.p.leblanc wrote:
I am getting linker errors with this stripped-down example:
---
**my_main.d:**
import std.stdio;
import std.complex;
import my_module;
void main(){
my_TYPE xxx;
wr
I am getting linker errors with this stripped-down example:
---
**my_main.d:**
import std.stdio;
import std.complex;
import my_module;
void main(){
my_TYPE xxx;
writeln(xxx);
}
---
**my
On Thursday, 14 May 2020 at 16:09:16 UTC, solidstate1991 wrote:
When I try to compile my own project under Ubuntu with dub, I
get the following linker error:
/usr/bin/ld: .dub/obj/pixelperfectengine_pixelperfecteditor.o:
undefined reference to symbol 'inflateEnd'
//lib/x86_64
On Friday, 15 May 2020 at 23:49:37 UTC, solidstate1991 wrote:
Dub should do the linking by itself.
How does it know what to link?
On Friday, 15 May 2020 at 03:46:57 UTC, evilrat wrote:
Um, pardon the stupid question, but did you just forgot to link
it? I can't see a mention of it anywhere in both the old json
and dub.sdl, and I don't see subpackages either. (does it links
implicitly by the compiler?)
Also if it's digg
On Thursday, 14 May 2020 at 16:09:16 UTC, solidstate1991 wrote:
When I try to compile my own project under Ubuntu with dub, I
get the following linker error:
/usr/bin/ld: .dub/obj/pixelperfectengine_pixelperfecteditor.o:
undefined reference to symbol 'inflateEnd'
//lib/x86_64
When I try to compile my own project under Ubuntu with dub, I get
the following linker error:
/usr/bin/ld: .dub/obj/pixelperfectengine_pixelperfecteditor.o:
undefined reference to symbol 'inflateEnd'
//lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO
missing from co
On 2019-05-30 15:36:53 +, Robert M. Münch said:
I updated to the latest DMD compiler and just re-compiled a project and
now I get two unresolved external errors:
widgets.obj : error LNK2001: Nicht aufgelöstes externes Symbol
"_D6object__T10RTInfoImplVAmA2i48i57ZQyyG2m".
widgets.obj : erro
On 2019-05-30 16:06:48 +, KnightMare said:
immutable(ulong[2]) object.RTInfoImpl!([48, 57]).RTInfoImpl
immutable(ulong[2]) object.RTInfoImpl!([32, 14]).RTInfoImpl
through
writeln( demangle("_D6object__T10RTInfoImplVAmA2i48i57ZQyyG2m"));
writeln( demangle("_D6object__T10RTInfoImplVAmA2i32i14Z
widgets.obj : error LNK2001: Nicht aufgelöstes externes Symbol
"_D6object__T10RTInfoImplVAmA2i48i57ZQyyG2m".
widgets.obj : error LNK2001: Nicht aufgelöstes externes Symbol
"_D6object__T10RTInfoImplVAmA2i32i14ZQyyG2m".
immutable(ulong[2]) object.RTInfoImpl!([48, 57]).RTInfoImpl
immutable(ulong
I updated to the latest DMD compiler and just re-compiled a project and
now I get two unresolved external errors:
widgets.obj : error LNK2001: Nicht aufgelöstes externes Symbol
"_D6object__T10RTInfoImplVAmA2i48i57ZQyyG2m".
widgets.obj : error LNK2001: Nicht aufgelöstes externes Symbol
"_D6obje
On Friday, 5 April 2019 at 22:08:50 UTC, Adam D. Ruppe wrote:
Weird combination of cases that maybe should be illegal.
It errors with the highly descriptive errormessage:
app.obj(app)
Error 42: Symbol Undefined __D8mymodule3BarFZ3fooMFZCQx3Foo
Error: linker exited with status 1
On Friday, 5 April 2019 at 21:59:35 UTC, Sjoerd Nijboer wrote:
Foo Bar()
{
Foo foo();
It looks like the compiler is treating that as a function
prototype without a body (that just happens to be nested in
another function).
return foo;
And then, this foo is given the optio
module mymodule;
class Foo{}
Foo Bar()
{
Foo foo();
return foo;
}
int main()
{
auto foo = Bar();
return 0;
}
This code doesn't compile with a linker error that there's a
missing symbol for `Foo Bar()` on windows.
After all, `Foo foo();` isn&#x
issue was in the generated xtoHash
function.
What version of the compiler are you using? My issue was fixed in
2.080.1, and then a followup fix in 2.081.1.
Ok, I get the same linker error down to version 2.74. Below that my
eventcore version does not compile. Atleast LDC can compile so I
On Monday, 21 January 2019 at 22:31:15 UTC, H. S. Teoh wrote:
On Mon, Jan 21, 2019 at 10:19:00PM +, Jerry via
Digitalmars-d-learn wrote:
On Monday, 21 January 2019 at 21:37:22 UTC, H. S. Teoh wrote:
[...]
> Looks like a problem with stale cached object files. Try:
>
> rm dub.selections.
On Mon, Jan 21, 2019 at 10:19:00PM +, Jerry via Digitalmars-d-learn wrote:
> On Monday, 21 January 2019 at 21:37:22 UTC, H. S. Teoh wrote:
[...]
> > Looks like a problem with stale cached object files. Try:
> >
> > rm dub.selections.json
> > dub build --force
> >
> > (Be sure to back
xtoHash function.
What version of the compiler are you using? My issue was fixed
in 2.080.1, and then a followup fix in 2.081.1.
-Steve
Ok, I get the same linker error down to version 2.74. Below that
my eventcore version does not compile. Atleast LDC can compile so
I can move forward. I will
On Monday, 21 January 2019 at 21:37:22 UTC, H. S. Teoh wrote:
On Mon, Jan 21, 2019 at 04:02:23PM -0500, Steven Schveighoffer
via Digitalmars-d-learn wrote:
On 1/21/19 3:37 PM, Jerry wrote:
> [...]
[...]
> [...]
[...]
Looks like a problem with stale cached object files. Try:
rm dub.
On Monday, 21 January 2019 at 21:02:23 UTC, Steven Schveighoffer
wrote:
What version of the compiler are you using? My issue was fixed
in 2.080.1, and then a followup fix in 2.081.1.
-Steve
Hello!
I am using 2.084.
Interestingly it works with LDC 1.9 (frontend 2.79) and that just
works fine
On Mon, Jan 21, 2019 at 04:02:23PM -0500, Steven Schveighoffer via
Digitalmars-d-learn wrote:
> On 1/21/19 3:37 PM, Jerry wrote:
> > Hello, I am trying to compile a 1 year old project of mine which
> > uses htmld and vibed. But I get this weird linker error which does
> > not
On 1/21/19 3:37 PM, Jerry wrote:
Hello, I am trying to compile a 1 year old project of mine which uses
htmld and vibed. But I get this weird linker error which does not make
any sense to me atleast. I am using Windows 7 and dub.
htmld 0.3.6: target for configuration "library" is
Hello, I am trying to compile a 1 year old project of mine which
uses htmld and vibed. But I get this weird linker error which
does not make any sense to me atleast. I am using Windows 7 and
dub.
htmld 0.3.6: target for configuration "library" is up to date.
taggedalgebraic 0.10.
On Saturday, 1 September 2018 at 18:46:32 UTC, Nordlöw wrote:
Thanks! Is there usually only apps and not libs that are
supposed to have linker flags like these?
In this specific case, I'm not sure it's a good idea to set the
linker in the dub config. Does it absolutely require gold, i.e.,
not
On Thursday, 30 August 2018 at 20:36:02 UTC, kinke wrote:
On Thursday, 30 August 2018 at 19:41:38 UTC, Nordlöw wrote:
I'm using the tar.xz for x64 Linux. Ok?
You're explicitly adding `-link-internally` in your top-level
dub.sdl:
dflags "-link-internally" platform="linux-ldc" # use GNU gold
On Thursday, 30 August 2018 at 19:41:38 UTC, Nordlöw wrote:
I'm using the tar.xz for x64 Linux. Ok?
You're explicitly adding `-link-internally` in your top-level
dub.sdl:
dflags "-link-internally" platform="linux-ldc" # use GNU gold
linker
If you want to go with gold, as your comment sugg
On Thursday, 30 August 2018 at 16:12:24 UTC, kinke wrote:
Nope, I now think this is more likely an issue with the default
config (etc/ldc2.conf). It contains a new section for
WebAssembly, which specificies `-link-internally`, which seems
to be wrongly used for non-WebAssembly too in your case.
On Thursday, 30 August 2018 at 16:12:24 UTC, kinke wrote:
Nope, I now think this is more likely an issue with the default
config (etc/ldc2.conf). It contains a new section for
WebAssembly, which specificies `-link-internally`, which seems
to be wrongly used for non-WebAssembly too in your case.
Nope, I now think this is more likely an issue with the default
config (etc/ldc2.conf). It contains a new section for
WebAssembly, which specificies `-link-internally`, which seems to
be wrongly used for non-WebAssembly too in your case.
I take it you're not using an official package, but a dis
On Thursday, 30 August 2018 at 13:36:58 UTC, Per Nordlöw wrote:
[...]
LDC uses the C compiler as linker driver by default, exactly
because the linker needs some setup (default lib dirs etc.). So
this is almost certainly a dub issue.
On Thursday, 30 August 2018 at 13:36:58 UTC, Per Nordlöw wrote:
Recently the benchmark
https://github.com/nordlow/phobos-next/tree/master/benchmarks/containers/dub.sdl
[...]
There is a way to specify the linker to be used
```
-linker= - Linker to use
```
Recently the benchmark
https://github.com/nordlow/phobos-next/tree/master/benchmarks/containers/dub.sdl
run as
dub run --compiler=ldc2 --build=release
has started to fail as
Performing "release" build using ldc2 for x86_64.
phobos-next ~master: target for configuration "library" is up to
On Sunday, 1 July 2018 at 01:16:59 UTC, Jonathan M Davis wrote:
On Sunday, July 01, 2018 00:42:30 spikespaz via
Digitalmars-d-learn wrote:
Hey guys, I'm getting a linker error when compiling with DMD
`-m63` that I don't get as 23 bit.
I'm importing `ShowWindow` from `core.sys.
On Sunday, July 01, 2018 00:42:30 spikespaz via Digitalmars-d-learn wrote:
> Hey guys, I'm getting a linker error when compiling with DMD
> `-m63` that I don't get as 23 bit.
>
> I'm importing `ShowWindow` from `core.sys.windows.winuser`, and I
> get the following:
Hey guys, I'm getting a linker error when compiling with DMD
`-m63` that I don't get as 23 bit.
I'm importing `ShowWindow` from `core.sys.windows.winuser`, and I
get the following:
C:\D\dmd2\windows\bin\lld-link.exe: warning: main.obj: undefined
symbol: ShowWindow
error: li
On Friday, 9 March 2018 at 13:46:33 UTC, Chris wrote:
I got this error msg today (see below):
DUB version 1.8.0, built on Mar 3 2018
vibe.d version 0.8.3
dmd 2.078.3 (the same with 2.079.0 and 2.077.0)
.dub/build/server64_72_debug-debug-linux.posix-x86_64-dmd_2079-CAC4A12AC8FE4B4625A9511E4EFEB
I got this error msg today (see below):
DUB version 1.8.0, built on Mar 3 2018
vibe.d version 0.8.3
dmd 2.078.3 (the same with 2.079.0 and 2.077.0)
.dub/build/server64_72_debug-debug-linux.posix-x86_64-dmd_2079-CAC4A12AC8FE4B4625A9511E4EFEB8F6/anscealai.o:
In function
`_D3std5range10primitive
On Sunday, 17 December 2017 at 20:09:02 UTC, ParticlePeter wrote:
On Sunday, 17 December 2017 at 19:29:00 UTC, ParticlePeter
wrote:
On Sunday, 17 December 2017 at 19:16:02 UTC, ParticlePeter
[snip]
LINKCMD=%VCINSTALLDIR%\bin\HostX32\x64\link.exe
or
LINKCMD=%VCINSTALLDIR%\bin\HostX64\x64\link
On Sunday, 17 December 2017 at 19:29:00 UTC, ParticlePeter wrote:
On Sunday, 17 December 2017 at 19:16:02 UTC, ParticlePeter
wrote:
On Sunday, 17 December 2017 at 17:56:47 UTC, John wrote:
I don't think so, all that would need to be changed is this
line:
https://github.com/dlang/dmd/blob/v2.
On Sunday, 17 December 2017 at 19:16:02 UTC, ParticlePeter wrote:
On Sunday, 17 December 2017 at 17:56:47 UTC, John wrote:
I don't think so, all that would need to be changed is this
line:
https://github.com/dlang/dmd/blob/v2.077.1/ini/windows/bin/sc.ini#L53
Not very many people use it I gue
On Sunday, 17 December 2017 at 17:56:47 UTC, John wrote:
I don't think so, all that would need to be changed is this
line:
https://github.com/dlang/dmd/blob/v2.077.1/ini/windows/bin/sc.ini#L53
Not very many people use it I guess if it's been there for 8
months lol.
Hm, actually that line I
On Sunday, 17 December 2017 at 17:15:57 UTC, ParticlePeter wrote:
On Sunday, 17 December 2017 at 16:40:46 UTC, John wrote:
Yah the sc.ini file is wrong for Environment64.
[Environment64]
LIB="%@P%\..\lib64"
.
.
.
; Windows installer uncomments the version detected
LINKCMD=%VCINSTALLDIR%\bin\
On Sunday, 17 December 2017 at 16:40:46 UTC, John wrote:
Yah the sc.ini file is wrong for Environment64.
[Environment64]
LIB="%@P%\..\lib64"
.
.
.
; Windows installer uncomments the version detected
LINKCMD=%VCINSTALLDIR%\bin\HostX86\x86\link.exe
Thanks! Is this a known, reported bug?
On Sunday, 17 December 2017 at 15:57:08 UTC, ParticlePeter wrote:
I upgraded from DMD 2.074.1 (!) to 2.077.1 and tried to compile
a mixed c++/d project (DMD links to one c++ lib). Here is the
full error message:
fatal error C1905: Front end and back end not compatible (must
target same proces
On Sunday, 17 December 2017 at 15:57:08 UTC, ParticlePeter wrote:
I upgraded from DMD 2.074.1 (!) to 2.077.1 and tried to compile
a mixed c++/d project (DMD links to one c++ lib). Here is the
full error message:
Forgot most important info, ita an x64 project those used VS
linker by default af
I upgraded from DMD 2.074.1 (!) to 2.077.1 and tried to compile a
mixed c++/d project (DMD links to one c++ lib). Here is the full
error message:
fatal error C1905: Front end and back end not compatible (must
target same processor).
LINK : fatal error LNK1257: code generation failed
Error: li
On Wednesday, 7 June 2017 at 09:55:24 UTC, Basile B. wrote:
On Wednesday, 7 June 2017 at 09:50:41 UTC, Basile B. wrote:
bla bla bla
Actually it's this code:
void main(string[] args)
{
import std.stdio;
import std.compiler;
writeln(vendor);
}
that gives the error. I suspect a regr
On Wednesday, 7 June 2017 at 09:50:41 UTC, Basile B. wrote:
bla bla bla
Actually it's this code:
void main(string[] args)
{
import std.stdio;
import std.compiler;
writeln(vendor);
}
that gives the error. I suspect a regression.
This is my script:
HOST_DMD=dmd
MODEL=64
cd dmd
make -fposix.mak MODEL=64 clean
make -fposix.mak ENABLE_RELEASE=1 MODEL=64 DMD=../dmd/src/dmd -j 5
cd ../druntime
make -fposix.mak MODEL=64 clean
make -fposix.mak MODEL=64 DMD=../dmd/src/dmd -j 5
cd ../phobos
make -fposix.mak MODEL=64 clean
mak
Dne 8.11.2016 v 21:16 Bryce Kellogg via Digitalmars-d-learn napsal(a):
...
Finally, a one line package.d:
public import my_package.my_module;
Change it to:
module my_package;
public import my_package.my_module;
Btw, having class name same as module name is not best way, there could
be some
tingly, if I remove the 'import std.stdio;' and writeln()
from my_module.d, it compiles fine. It also works if I move the
import down to inside the constructor, or replace the import in
app.d with 'import my_package.my_module;' (side stepping the
package.d).
To summarize: i
ray,
std.conv in the module.
(.data._D65TypeInfo_xC3std5range10interfaces18__T10InputRangeTiZ10InputRange6__initZ+0x10):
undefined reference to
`_D64TypeInfo_C3std5range10interfaces18__T10InputRangeTiZ10InputRange6__initZ'
collect2: error: ld returned 1 exit status
This linker error i
.conv in the module.
(.data._D65TypeInfo_xC3std5range10interfaces18__T10InputRangeTiZ10InputRange6__initZ+0x10):
undefined reference to
`_D64TypeInfo_C3std5range10interfaces18__T10InputRangeTiZ10InputRange6__initZ'
collect2: error: ld returned 1 exit status
This linker error is saying it can't find a required typeinfo
initializer for std.range.in
On Friday, 10 June 2016 at 13:04:32 UTC, Chris wrote:
It doesn't compile with
`dmd file1.d file2.d`
either. I'll have to look into this. Weird.
looks like a clear sign of dmd versions conflict. most of the
time things like that caused by some leftover from previous dmd —
like old libphobos.
On Friday, 10 June 2016 at 12:52:05 UTC, Chris wrote:
I use dub and `dvm use 2.071.0`.
hm. sorry, i can't help you with this. straight "dmd test.d" is
ok, so it's probably something with dub/dvm interaction...
On Friday, 10 June 2016 at 13:00:23 UTC, ketmar wrote:
On Friday, 10 June 2016 at 12:52:05 UTC, Chris wrote:
I use dub and `dvm use 2.071.0`.
hm. sorry, i can't help you with this. straight "dmd test.d" is
ok, so it's probably something with dub/dvm interaction...
It doesn't compile with
`
On Friday, 10 June 2016 at 12:12:17 UTC, ketmar wrote:
On Friday, 10 June 2016 at 12:04:50 UTC, Chris wrote:
I get the error below with code like this:
auto res = ['1', '2'].map!(a => a.to!string);
dmd 2.071.0
What's wrong here? I import std.algorithm, std.range,
std.array, std.conv in the m
On Friday, 10 June 2016 at 12:04:50 UTC, Chris wrote:
I get the error below with code like this:
auto res = ['1', '2'].map!(a => a.to!string);
dmd 2.071.0
What's wrong here? I import std.algorithm, std.range,
std.array, std.conv in the module.
(.data._D65TypeInfo_xC3std5range10interfaces18_
I get the error below with code like this:
auto res = ['1', '2'].map!(a => a.to!string);
dmd 2.071.0
What's wrong here? I import std.algorithm, std.range, std.array,
std.conv in the module.
(.data._D65TypeInfo_xC3std5range10interfaces18__T10InputRangeTiZ10InputRange6__initZ+0x10):
undefined
On Monday, 6 June 2016 at 02:21:03 UTC, docandrew wrote:
On Sunday, 5 June 2016 at 21:26:56 UTC, Anonymous wrote:
On Sunday, 5 June 2016 at 21:16:36 UTC, Andrej Mitrovic wrote:
On 6/5/16, Anonymous via Digitalmars-d-learn
wrote:
[...]
You can report it here: https://issues.dlang.org
[...]
On Sunday, 5 June 2016 at 21:26:56 UTC, Anonymous wrote:
On Sunday, 5 June 2016 at 21:16:36 UTC, Andrej Mitrovic wrote:
On 6/5/16, Anonymous via Digitalmars-d-learn
wrote:
Should I report this as a dmd bug then? Not sure where / how
to do that.
You can report it here: https://issues.dlang.or
On Sunday, 5 June 2016 at 21:16:36 UTC, Andrej Mitrovic wrote:
On 6/5/16, Anonymous via Digitalmars-d-learn
wrote:
Should I report this as a dmd bug then? Not sure where / how
to do that.
You can report it here: https://issues.dlang.org
I think I'll just let it go; I was able to work passed
On 6/5/16, Anonymous via Digitalmars-d-learn
wrote:
> Should I report this as a dmd bug then? Not sure where / how to
> do that.
You can report it here: https://issues.dlang.org
> I think I'll just let it go; I was able to work passed it anyway
> using "static Note[] empty;", and `null` works to
On Sunday, 5 June 2016 at 20:16:54 UTC, Andrej Mitrovic wrote:
On 6/5/16, Anonymous via Digitalmars-d-learn
wrote:
static Note[0] empty;
Note[] getNotes(string id)
{
return (id in store) ? store[id] : empty;
}
It's likely an accepts-invalid bug
On 6/5/16, Anonymous via Digitalmars-d-learn
wrote:
> static Note[0] empty;
>
> Note[] getNotes(string id)
> {
> return (id in store) ? store[id] : empty;
> }
It's likely an accepts-invalid bug, meaning it should be a compiler
error instead. I d
1 - 100 of 259 matches
Mail list logo
