View previous topic :: View next topic |
Author |
Message |
mmcdermo
Joined: 09 Nov 2006 Posts: 18
|
Posted: Mon Dec 18, 2006 7:17 pm Post subject: Possible bug (or application flaw): linking in std.c..... |
|
|
In std.c.linuxextern.d, it is written:
Code: |
/* These are all the globals defined by the linux C runtime library.
* Put them separate so they'll be externed - do not link in linuxextern.o
*/
|
Build gave linuxextern.o to the linker as a file to link... Is this a problem with my application, or bud? ( I get a linker error of multiple definitions caused by linuxextern.o when I attempt to build this app. )
Note: I do not explicitly import std.c.linuxextern. |
|
Back to top |
|
|
csauls
Joined: 27 Mar 2004 Posts: 278
|
Posted: Tue Dec 19, 2006 4:16 pm Post subject: |
|
|
I believe you should be able to just add "-Xstd.c.linuxextern" to your Build command line or BRF file and be set. If I remember right how the "-X" switch can be used. _________________ Chris Nicholson-Sauls |
|
Back to top |
|
|
Derek Parnell
Joined: 22 Apr 2004 Posts: 408 Location: Melbourne, Australia
|
Posted: Tue Dec 19, 2006 5:44 pm Post subject: |
|
|
You may not have read the answer I gave to the problem you reported earlier with the pragma.
Quote: | However, I can see you are also compiling all the phobos modules too. By default, it expects that the phobos modules are kept in a directory with the word 'phobos' in it, and thus excludes them from recompiling. You can alter this by adding -Xdmdincludes to either the Bud command line or more conveniently to the Bud configuration file - build.cfg. See the docs for details. |
_________________ --
Derek
skype name: derek.j.parnell |
|
Back to top |
|
|
mmcdermo
Joined: 09 Nov 2006 Posts: 18
|
Posted: Thu Dec 21, 2006 11:25 am Post subject: |
|
|
Hah! Thanks for the explanation Derek... I didn't make the connection |
|
Back to top |
|
|
|