If I compile with rdmd
```
$ dub build --rdmd
```
it works
iguration "library", build type
debug.
Running dmd...
Building ddb_test ~master configuration "application", build type
debug.
Compiling using dmd...
Linking...
```
I get a message:
Unexpected OPTLINK Termination a t EIP=0040F5Ba
If I comment just a row on app.d:
```
import ddb.postgres;
// import gtk.Window; <=
int main(string[] argv) {
return 0;
}
```
it works!
Thank you
I'm getting "Unexpected OPTLINK Termination at EIP = 0
and assembly register values" when compiling the follow code. I'm
doing something wrong?
class MyClass
{
void opCall()
{
}
}
public void main(string[] arguments)
{
MyClass clazz = new MyClass();
On 2012-10-09 22:59, Andrei Alexandrescu wrote:
I'd be bummed because that's quite a logical decision, and how other
interpreters do it.
GDB uses the --args approach.
--
/Jacob Carlborg
On 09/10/2012 22:30, Andrei Alexandrescu wrote:
On 10/9/12 12:30 PM, Faux Amis wrote:
On a side-note, why is rdmd picky about argument order?
>dmd test.d -I..\include
Because anything after the program is considered an argument to the
program.
Andrei
My bad, should have read the spec bett
On 10/9/12, Andrei Alexandrescu wrote:
> I'd be bummed because that's quite a logical decision, and how other
> interpreters do it.
On second thought my solution wouldn't work. --args would still have
to be passed before the D file, and people would have to remember that
or it wouldn't work, same
On 10/9/12 4:38 PM, Andrej Mitrovic wrote:
On 10/9/12, Andrei Alexandrescu wrote:
On 10/9/12 12:30 PM, Faux Amis wrote:
On a side-note, why is rdmd picky about argument order?
>dmd test.d -I..\include
Because anything after the program is considered an argument to the
program.
Andrei
On 10/9/12, Andrei Alexandrescu wrote:
> On 10/9/12 12:30 PM, Faux Amis wrote:
>> On a side-note, why is rdmd picky about argument order?
>>
>> >dmd test.d -I..\include
>
> Because anything after the program is considered an argument to the
> program.
>
> Andrei
>
I think this is a fairly common
On 10/9/12 12:30 PM, Faux Amis wrote:
On a side-note, why is rdmd picky about argument order?
>dmd test.d -I..\include
Because anything after the program is considered an argument to the program.
Andrei
I get an unexpected OPTLINK termination when I run the lovely thing
below, any advice (dmd 2.060)?
rdmd --chatty --force --build-only ..\lib\libcairo-2.lib -I..\include
..\lib\libcairod.lib ..\lib\dmd_win32_x32.lib -version=Unicode
-version=WIN32_WINNT_ONLY -version=WindowsNTonly -version
On Monday, 20 August 2012 at 13:50:27 UTC, Philippe Sigaud wrote:
On Mon, Aug 20, 2012 at 7:33 AM, cal
wrote:
I don't think I can narrow down this problem easily, I suspect
the problem
is in a 11k lines module of template heavy code generated by
Pegged. I am
just wondering if anyone who saw
On Mon, Aug 20, 2012 at 7:33 AM, cal wrote:
> I don't think I can narrow down this problem easily, I suspect the problem
> is in a 11k lines module of template heavy code generated by Pegged. I am
> just wondering if anyone who saw this problem pre the git commit also has
> trouble with debug bui
I just ran into (I think) this bug
http://d.puremagic.com/issues/show_bug.cgi?id=8377 using dmd
2.060. Seeing that there was a fix in git, I cloned the latest
git dmd, built, and dropped the .exe into my existing dmd 2.060
installation directory.
I still get this unexpected optlink
13 matches
Mail list logo
