Re: what am I missing here with that working dir?

2019-03-18 Thread DFTW via Digitalmars-d-learn
On Saturday, 16 March 2019 at 07:27:43 UTC, FreeSlave wrote: On Friday, 15 March 2019 at 21:48:50 UTC, DFTW wrote: What am I missing here? Maybe the terminal and your utility you run wkhtmltopdf from have different environment? I guessed so, I've tried set the env as well: enum env =

Re: what am I missing here with that working dir?

2019-03-18 Thread DFTW via Digitalmars-d-learn
On Monday, 18 March 2019 at 15:39:39 UTC, Andre Pany wrote: On Monday, 18 March 2019 at 15:23:46 UTC, DFTW wrote: On Saturday, 16 March 2019 at 07:27:43 UTC, FreeSlave wrote: On Friday, 15 March 2019 at 21:48:50 UTC, DFTW wrote: What am I missing here? Maybe the terminal and your utility

Re: build 32-bit library on 64-bit OS

2019-03-19 Thread DFTW via Digitalmars-d-learn
On Tuesday, 19 March 2019 at 20:31:46 UTC, kinke wrote: On Tuesday, 19 March 2019 at 17:23:21 UTC, DFTW wrote: /usr/bin/ld: skiping //usr/lib/x86_64-linux-gnu/libphobos2-ldc-shared.so incompatible to -lphobos2-ldc-shared /usr/bin/ld: couldn't find -lphobos2-ldc-shared If possible, use an

Re: build 32-bit library on 64-bit OS

2019-03-20 Thread DFTW via Digitalmars-d-learn
On Tuesday, 19 March 2019 at 21:20:24 UTC, kinke wrote: On Tuesday, 19 March 2019 at 20:56:47 UTC, DFTW wrote: What package did you mean? that libphobos2 on the error messages from the ld? I'm using dmd/dub on Ubuntu 18. libphobos2-ldc-shared.so is definitely from LDC. I hadn't noticied it

Re: SEGFAULT when converting C string to string

2019-03-18 Thread DFTW via Digitalmars-d-learn
On Monday, 18 March 2019 at 22:33:21 UTC, H. S. Teoh wrote: On Mon, Mar 18, 2019 at 10:20:35PM +, DFTW via Digitalmars-d-learn wrote: [...] [...] Most likely explanation: you failed to call rt_init() before using a language feature that requires druntime to be initialized. In this case

SEGFAULT when converting C string to string

2019-03-18 Thread DFTW via Digitalmars-d-learn
I'm writing a shared library in C to be used from a C program, so I went to my small tests. That one failed give a SEGFAULT on the std.conv.to call. This is the pice of D code/the library: extern(C) int foo(const char *name, int age) { import core.stdc.stdio : printf; import

build 32-bit library on 64-bit OS

2019-03-19 Thread DFTW via Digitalmars-d-learn
So I need to build a 32-bit version of a library on 64-bit system. I got some errors, which I get rid of after installing the gcc 32-bit tools (and gcc -m32 ran fine) but I still get errors about libraries not compatible. the command: dub --arch=x86 yield erros such: /usr/bin/ld: skiping

am I using version right?

2019-03-12 Thread DFTW via Digitalmars-d-learn
version(Windows) { writeln("Hello from Windows system!"); } else version(linux) { writeln("hello from linux!"); } else static assert(0, "unknow system!"); In that code, the static assert() will run if and

what am I missing here with that working dir?

2019-03-15 Thread DFTW via Digitalmars-d-learn
I'd like to call a executable which works fine on terminal if called within the bin directory otherwise it give missing issues. To archive the same on my D program, I did set the working dir but I get an error saying a .so file couldn't be found. What am I missing here? enum app =