On Apr 19, 2014, at 4:11 AM, Thomas Hoffmann <trh...@gmail.com> wrote:
> On Sat, Apr 19, 2014 at 2:27 AM, Jung-uk Kim <j...@freebsd.org> wrote:
>> On 2014-04-19 02:14:58 -0400, Thomas Hoffmann wrote:
>>> On Sat, Apr 19, 2014 at 1:05 AM, Jung-uk Kim <j...@freebsd.org
>>> <mailto:j...@freebsd.org>> wrote:
>>> On 2014-04-18 23:46:46 -0400, Thomas Hoffmann wrote:
>>>> After building at -CURRENT amd64 r264673, I got the following
>>>> errors running 'make delete-old' and 'make delete-old-libs':
>>> This should be fixed in r264674.
>>> Jung-uk Kim
>>> With r264674, I no longer see those errors reported at delete-old or
>>> delete-old-libs, however, I now see those errors reported at the
>>> beginning of buildworld, buildkernel, installkernel, and installworld.
>>> With r264673 I only saw the errors at delete-old and delete-old-libs.
>> I can't reproduce it. Do you have the bsd.mkopt.mk in /usr/share/mk,
>> i.e., did you do installworld?
>> Jung-uk Kim
> Had I taken a bit more time to think on it before my last post, I would
> have realized that what I was seeing is exactly what I should have
> expected. In order to reproduce my problem, you would have had to build at
> r264673 and then again at r264674.
> When I built at r264673, I was using the last good *.mk installed from
> r264633. That is why I did not see the errors for buildworld, buildkernel,
> installkernel and installworld. But, since installworld at r264673
> installed the bad *.mk, that is why I saw the errors for the subsequent
> delete-old and delete-old-libs.
> When I re-built at r264674, I was still using the bad *.mk installed from
> r264673. That is why I saw the errors for buildworld, buildkernel,
> installkernel and installworld. But, since installworld at r264674
> installed the good (i.e., fixed) *.mk, that is why I no longer saw the
> errors for the subsequent delete-old and delete-old-libs.
bad mk files?
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"