Hallo,

I think you might be interested in this. Attached are the ebuilds.
All you have to do is extract this file inside your portage overlay dir.
I don't know why it doesn't work. Everything compiles and gets installed
  but something goes wrong. Maybe you can help me...

Stephan

Stephan Wienczny wrote:
> Hallo,
> 
> I think you might be interested in this. Attached are the ebuilds.
> All you have to do is extract this file inside your portage overlay dir.
> I don't know why it doesn't work. Everything compiles and gets installed  but something goes wrong. Maybe you can help me...
> 
> Stephan
I have the same problems Stephan. Here's the last part of an strace:


access("/tmp", R_OK|W_OK|X_OK)          = 0
gettimeofday({1083130059, 153688}, NULL) = 0
getpid()                                = 5584
open("/tmp/ccPdmHZj.s", O_RDWR|O_CREAT|O_EXCL, 0600) = 3
close(3)                                = 0
stat64("/usr/libexec/gcc/i686-pc-linux-gnu/3.4.0/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/libexec/gcc/i686-pc-linux-gnu/3.4.0/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/libexec/gcc/i686-pc-linux-gnu/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/gcc/i686-pc-linux-gnu/3.4.0/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/gcc/i686-pc-linux-gnu/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/libexec/gcc/i686-pc-linux-gnu/3.4.0/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/libexec/gcc/i686-pc-linux-gnu/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/gcc/i686-pc-linux-gnu/3.4.0/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/gcc/i686-pc-linux-gnu/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/../i686-pc-linux-gnu/bin/i686-pc-linux-gnu/3.4.0/cc1d", 0xbfffee58) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/../i686-pc-linux-gnu/bin/cc1d", 0xbfffee60) = -1 ENOENT (No such file or directory)
fork(Error: Error reading file 'object.d'

)                                  = 5585
--- SIGCHLD (Child exited) @ 0 (0) ---
waitpid(5585, [WIFEXITED(s) && WEXITSTATUS(s) == 1], 0) = 5585
stat64("/tmp/ccPdmHZj.s", {st_mode=S_IFREG|0600, st_size=22, ...}) = 0
unlink("/tmp/ccPdmHZj.s")               = 0
exit_group(1)

Dan

Dan Milne wrote:
> Stephan Wienczny wrote:
> 
>> Hallo,
>>
>> I think you might be interested in this. Attached are the ebuilds.
>> All you have to do is extract this file inside your portage overlay dir.
>> I don't know why it doesn't work. Everything compiles and gets
>> installed  but something goes wrong. Maybe you can help me...
>>
>> Stephan
> 
> I have the same problems Stephan. Here's the last part of an strace:
> 
> 
> Dan

Thanks Dan that helped a lot... I did not know what tools I had...
I moved cc1d to /usr/lib/gcc/i686-pc-linux/3.3.3 and downgraded to
3.3.3, my system's standard compiler.
I got a small test app to compile.
All I had to do was:
gdc -lgc -ldl -o <filename> <filename.d>
I don't know why I had to link against boehm-gc.
nm tells me that the missing symbols are undefined....

Stephan

Stephan Wienczny wrote:
> Dan Milne wrote:
> 
>> Stephan Wienczny wrote:
>>
>>> Hallo,
>>>
>>> I think you might be interested in this. Attached are the ebuilds.
>>> All you have to do is extract this file inside your portage overlay dir.
>>> I don't know why it doesn't work. Everything compiles and gets installed  but something goes wrong. Maybe you can help me...
>>>
>>> Stephan
>>
>>
>> I have the same problems Stephan. Here's the last part of an strace:
>>
>>
>> Dan
> 
> 
> Thanks Dan that helped a lot... I did not know what tools I had...
> I moved cc1d to /usr/lib/gcc/i686-pc-linux/3.3.3 and downgraded to 3.3.3, my system's standard compiler.
> I got a small test app to compile.
> All I had to do was:
> gdc -lgc -ldl -o <filename> <filename.d>
> I don't know why I had to link against boehm-gc.
> nm tells me that the missing symbols are undefined....
> 
> Stephan

There shouldn't be any need to link against boehm-gc unless something else (C++?) is requiring it.  If the dependency is in Phobos, it's not being built correctly. Also, the D and boehm garbage collectors probably won't work in the same program.

David

Stephan Wienczny wrote:
> 
> Thanks Dan that helped a lot... I did not know what tools I had...
> I moved cc1d to /usr/lib/gcc/i686-pc-linux/3.3.3 and downgraded to 3.3.3, my system's standard compiler.
> I got a small test app to compile.
> All I had to do was:
> gdc -lgc -ldl -o <filename> <filename.d>
> I don't know why I had to link against boehm-gc.
> nm tells me that the missing symbols are undefined....
> 
> Stephan

Glad it helped. I can build now with gdc using -lgc -ldl as you do.

To build with dmd, I need to:

dmd -L-lgc -L-ldl wc.d

So perhaps the dependency is in Phobos?

Cheers,

Dan

On Wed, 28 Apr 2004 23:14:45 +0200
Stephan Wienczny <wienczny@web.de> wrote:

> Dan Milne wrote:
> > Stephan Wienczny wrote:
> > 
> >> Hallo,
> >>
> >> I think you might be interested in this. Attached are the ebuilds.
> >> All you have to do is extract this file inside your portage overlay dir.
> >> I don't know why it doesn't work. Everything compiles and gets
> >> installed  but something goes wrong. Maybe you can help me...
> >>
> >> Stephan
> > 
> > I have the same problems Stephan. Here's the last part of an strace:
> > 
> > 
> > Dan
> 
> Thanks Dan that helped a lot... I did not know what tools I had...
> I moved cc1d to /usr/lib/gcc/i686-pc-linux/3.3.3 and downgraded to
> 3.3.3, my system's standard compiler.
> I got a small test app to compile.
> All I had to do was:
> gdc -lgc -ldl -o <filename> <filename.d>
> I don't know why I had to link against boehm-gc.
> nm tells me that the missing symbols are undefined....
> 
> Stephan
> 
Hi,
I've changed some static values regarding gcc in the ebuilds so it will work with 3.3.2, 3.3.3 and 3.4.0
do you think it will be a good idea to add -ldl to the libphobos.spec?

bye