[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: kdenetwork/ktalkd/ktalkd
From:       Eray Ozkural <eozk () bicom-inc ! com>
Date:       2003-01-02 8:03:00
[Download RAW message or body]

On Wednesday 01 January 2003 11:34 am, David Faure wrote:
> On Tuesday 31 December 2002 13:38, Eray Ozkural wrote:
> > On Tuesday 31 December 2002 08:55 pm, Marc Mutz wrote:
> > > On Tuesday 31 December 2002 19:06, Eray Ozkural wrote:
> > > > +print.cpp: print.c
> > > > +        rm -f print.cpp
> > > > +        ln -s print.c print.cpp
> > > > +
> > > > +repairs.cpp: repairs.c
> > > > +        rm -f repairs.cpp
> > > > +        ln -s repairs.c repairs.cpp
> > >
> > > Shouldn't that be
> > > ln -s $(srcdir)/foo.c foo.cpp
> > > ?
>
> And it should be $(LN_S) instead of ln -s, if this hack remains in.
>
> > Yea I'd thought like that but seeing this worked for me I did it that
> > way.
>
> Which only proves you're not using srcdir!=builddir.
>

Strange, I did use srcdir!=buildir, it should be
 $(LN_S) $(srcdir)/foo.c $(srcdir)/foo.cpp

I suppose

>
> Did you try my suggestion?
> Are you sure this hack is necessary, or is it only due to the stale .deps
> files? (In the absence of answer, I will revert this change, I don't want
> to be bothered with bugs in it, as the maintainer, when AFAIK there's no
> need for such a hack)

I just read it, but I had removed the entire ktalkd from build dir and 
reconfigured before trying this silly patch.

Let me revert changes, and then try to replicate that bug making sure I remove 
the .deps. I'll tell the result

Cheers,

-- 
Eray Ozkural <eozk@bicom-inc.com>
Software Engineer, BICOM Inc.
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C

[prev in list] [next in list] [prev in thread] [next in thread]