Gregor
Joined: 05 May 2006
Posts: 72
Location: Portland, OR
|
 Posted: Thu Sep 28, 2006 5:05 pm Post subject: util/fdt.d on UNIXen |
 |
|
I think I already posted this to the NG, but it's fairly important so I'll post it here.
In util/fdt.d are the lines:
| Code: |
version(Windows) static import opsys = std.c.windows.windows;
version(linux) static import opsys = std.c.linux.linux;
version(darwin) static import opsys = std.c.darwin.darwin;
version(Unix) static import opsys = std.c.unix;
|
This fails on GNU/Linux and probably Mac OS X, because these situations need to be else'd - they're mutually exclusive:
| Code: |
version(Windows) static import opsys = std.c.windows.windows;
else version(linux) static import opsys = std.c.linux.linux;
else version(darwin) static import opsys = std.c.darwin.darwin;
else version(Unix) static import opsys = std.c.unix;
|
Otherwise it'll attempt to import multiple modules as "opsys", and get:
| Code: |
util/fdt.d:72: static import util.fdt.opsys package and module have the same name
util/fdt.d:72: module unix cannot read file 'std/c/unix.d'
util/fdt.d:72: static import util.fdt.opsys package and module have the same name
util/fdt.d:72: module unix cannot read file 'std/c/unix.d'
util/fdt.d:72: static import util.fdt.opsys package and module have the same name
util/fdt.d:72: module unix cannot read file 'std/c/unix.d'
|
Also, isn't that std.c.unix.unix? I have a std/c/unix/unix.d, but no std/c/unix.d. |
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
