RejectedSoftware Forums

Commit: c4ae00a

On Thu, 09 Oct 2014 08:14:27 GMT, Mickaël Bouchaud wrote:

On Thu, 02 Oct 2014 17:28:58 GMT, Sönke Ludwig wrote:

Commit: c4ae00a

I tried to test it and I have issues with dub.
I tried to upgrade dub dependencies with :

dub upgrade --force-remove

but I get this error

Fetching libevent 2.0.1+2.0.16...
Error executing command build: Failed to download http://code.dlang.org/packages/libevent/2.0.1%252B2.0.16.zip: 404 Not >Found

It seems that dub try to download libevent dependency from http://code.dlang.org/packages/libevent/2.0.1%252B2.0.16.zip instead of http://code.dlang.org/packages/libevent/2.0.1+2.0.16.zip

The url seems to have been encoded twice from

http://code.dlang.org/packages/libevent/2.0.1+2.0.16.zip
to
http://code.dlang.org/packages/libevent/2.0.1%2B2.0.16.zip
and to
http://code.dlang.org/packages/libevent/2.0.1%252B2.0.16.zip

I'm wondering how I can fix this or get around this problem. Any idea ?

How I can figure out if the problem is on the dub repository or on my local dub. Is there a discussion, forum or something for dub related problems ?

Thanks

Seems that an outdated dub was my problem here.

I updated dub to 0.9.22 and also DMD to 2.066.0.
I'm on vibe.d master branch.

I removed all packages in ~/.dub/packages/, run dub and get this error.

WARNING: A deprecated branch based version specification is used for the dependency vibe-d. Please use numbered versions instead. Also note that you can still use the dub.selections.json file to override a certain dependency to use a branch instead.
Building vibe-d ~master configuration "libevent", build type debug.
Running dmd...
Building testdouble ~master configuration "application", build type debug.
Compiling using dmd...
Linking...
Undefined symbols for architecture x86_64:
  "_D4core6thread5Fiber4callMFbZC6Object", referenced from:
      _D4vibe4core4core14VibeDriverCore14resumeCoreTaskMFC4vibe4core4core8CoreTaskC9ExceptionZv in libvibe-d.a(core_32c2_57b.o)
  "_D4core6thread6Thread7getThisFZC4core6thread6Thread", referenced from:
      _D4vibe4core3log6rawLogFNbNfAyaiE4vibe4core3log8LogLevelAyaZ9__lambda6FNeZC4core6thread6Thread in libvibe-d.a(log_343e_26c.o)
      _D4vibe4core4core18_sharedStaticCtor1FZv in libvibe-d.a(core.o)
      _D4vibe4core4core12_staticCtor3FZv in libvibe-d.a(core.o)
      _D4vibe4core4core12_staticDtor4FZv in libvibe-d.a(core.o)
      _D4vibe4core4core14VibeDriverCore14resumeCoreTaskMFC4vibe4core4core8CoreTaskC9ExceptionZv in libvibe-d.a(core_32c2_57b.o)
      _D4vibe4core4core17handleWorkerTasksFZv in libvibe-d.a(core_32ca_6ec.o)
      _D4vibe4core4core8CoreTask4joinMFZv in libvibe-d.a(core_32c1_31c.o)
      ...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
--- errorlevel 1

I copied the verbose version here

Any idea how to fix this problem ?

On Thu, 09 Oct 2014 21:00:47 +0200, Sönke Ludwig wrote:

That looks strange, those should be standard Phobos symbols.
Unfortunately I don't have a Mac available for testing until next week.
I'll see if I can reproduce the issue then.

As a complete shot in the dark, you could try to add "libs": <br>["phobos2"] to the dub.json of the "testdouble" package. As a sanity
check, does invoking dmd on the following produce any errors?

import core.thread;
void main()
{
	auto t = Thread.getThis();
	auto f = new Fiber({});
	f.call();
}

I tried this sanity check running dmd 2.066 and get an error message :

Undefined symbols for architecture x86_64:
  "_D4core6thread5Fiber4callMFbZC6Object", referenced from:
      __Dmain in test.o
  "_D4core6thread6Thread7getThisFZC4core6thread6Thread", referenced from:
      __Dmain in test.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
--- errorlevel 1

So it seems that it's a DMD problem then.