Quoting Ivan Shmakov (2014-04-06 11:15:06)
> > Justus Winter <4win...@informatik.uni-hamburg.de> writes:
>
> > The second issue is due to me doing an out-of-tree build. That it
> > currently works is more or less by chance I fear. I just came up
> > with a (legit in my opinion) patch that
> Justus Winter <4win...@informatik.uni-hamburg.de> writes:
> The second issue is due to me doing an out-of-tree build. That it
> currently works is more or less by chance I fear. I just came up
> with a (legit in my opinion) patch that breaks oot builds.
> So what happens here is that
Quoting Samuel Thibault (2014-04-05 23:42:23)
> Justus Winter, le Sat 05 Apr 2014 20:16:12 +0200, a écrit :
> > buildbot@pluto:/home/pluto/hurd/build/build-deb$ make -C libdiskfs || echo
> > $?
> > 2
> >
> > Yes, that's most helpful. Not.
>
> I've seen that too. It happens when the dep files ha
Justus Winter, le Sat 05 Apr 2014 20:16:12 +0200, a écrit :
> buildbot@pluto:/home/pluto/hurd/build/build-deb$ make -C libdiskfs || echo $?
> 2
>
> Yes, that's most helpful. Not.
I've seen that too. It happens when the dep files have a non-existing
entry. I usually use make -d to see what is mi
Hi :)
there are two build system issues that are driving me mad (well, the
first one at least).
buildbot@pluto:/home/pluto/hurd/build/build-deb$ make -C libdiskfs || echo $?
2
Yes, that's most helpful. Not.
buildbot@pluto:/home/pluto/hurd/build/build-deb/libdiskfs$ rm demuxer.d
buildbot@
