Justus Winter writes:
> And the build system I adopted doesn't actually use cp, I just
> demonstrated the problem using cp. Therefore, it is not as easy as
> using -a instead of -r.
>
> In any case, I'm just going to delete any .stamp files in my build
> process.
I would recommend that you
ni...@lysator.liu.se (Niels Möller) writes:
> Justus Winter writes:
>
>> I read the reference, and I don't see how it applies here.
>
> Right, it's a bit different.
>
>> For the
>> record, this is the build failure that I'm referring to:
>>
>> % tar xf nettle-3.5.1.tar.gz
>> % cp -r nettle-3.5.1
Justus Winter writes:
> I read the reference, and I don't see how it applies here.
Right, it's a bit different.
> For the
> record, this is the build failure that I'm referring to:
>
> % tar xf nettle-3.5.1.tar.gz
> % cp -r nettle-3.5.1 nettle
> % cd nettle
> % ./configure
> [...]
> % make
>
ni...@lysator.liu.se (Niels Möller) writes:
> Justus Winter writes:
>
>> just a small bug report, there are some .stamp files that got included
>> in the release by accident. I noticed because it caused build problems,
>> likely only due to the fact that my build process copied the files once,
Justus Winter writes:
> just a small bug report, there are some .stamp files that got included
> in the release by accident. I noticed because it caused build problems,
> likely only due to the fact that my build process copied the files once,
> changing the mtimes in the process.
Some stamp
Hi :)
just a small bug report, there are some .stamp files that got included
in the release by accident. I noticed because it caused build problems,
likely only due to the fact that my build process copied the files once,
changing the mtimes in the process.
% tar tf nettle-3.5.1.tar.gz |
