Date:Mon, 2 Jan 2023 10:39:45 +0100
From:Martin Husemann
Message-ID: <20230102093945.gb...@mail.duskware.de>
| Note that the official daily builds also use this (and have been failing
| since new binutils have been enabled for x86).
They should be back working
On Mon, Jan 02, 2023 at 12:17:11PM +1100, matthew green wrote:
> oh yeah - this is only going to break r/o src tree builds, which is
> also something i use as much as possible.
Note that the official daily builds also use this (and have been failing
since new binutils have been enabled for x86).
Date:Sun, 1 Jan 2023 19:17:54 -0800 (PST)
From:Paul Goyette
Message-ID:
| FWIW, touch(1)ing all copies of bfd.info gets us past the ``build.sh
| tools'' successfully. I have seen no new issues.
I just updated to get Matt's changes (no arbitrary touching in the
| can you update and post the latest failures?
Will do.
FWIW, touch(1)ing all copies of bfd.info gets us past the ``build.sh
tools'' successfully. I have seen no new issues.
++--+--+
| Paul Goyette | PGP Key fingerprint:
Date:Mon, 02 Jan 2023 12:17:11 +1100
From:matthew green
Message-ID: <10634.1672622...@splode.eterna.com.au>
| can you update and post the latest failures?
Will do.
kre
Robert Elz writes:
> I wonder if perhaps part of the reason (or perhaps all of it) that
> Paul and I see problems, where others aren't, is that we are both
> building from a read only mounted source tree.
oh yeah - this is only going to break r/o src tree builds, which is
also something i use as
Date:Mon, 02 Jan 2023 03:45:16 +1100
From:matthew green
Message-ID: <8109.1672591...@splode.eterna.com.au>
| it's not seen by most because it depends upon the timestamps of
| some files..
I am also having issues (with very recently updated sources).
I wonder if
> > Sources updated to 2022-12-31 at 13:42:04 UTC and all output dirs
> > (obj, release, dist, tools) were cleaned.
>
> Is no-one else seeing this problem with ``build.sh tools'' ?
it's not seen by most because it depends upon the timestamps of
some files.. my first attempt to fix it failed, i
> > Sources updated to 2022-12-31 at 13:42:04 UTC and all output dirs (obj,
> > release, dist, tools) were cleaned.
>
> Is no-one else seeing this problem with ``build.sh tools'' ?
it's not seen by most because it depends upon the timestamps of
some files.. my first attempt to fix it failed, i
On Sat, 31 Dec 2022, Paul Goyette wrote:
Sources updated to 2022-12-31 at 13:42:04 UTC and all output dirs (obj,
release, dist, tools) were cleaned.
Is no-one else seeing this problem with ``build.sh tools'' ?
===> build.sh command:./build.sh -T
/build/netbsd-current/tools/x86_64/amd64
On 31 December 2022 19:44:05 (+00:00), Paul Goyette wrote:
> Sources updated to 2022-12-31 at 13:42:04 UTC and all output dirs (obj,
> release, dist, tools) were cleaned.
>
> ``build.sh tools'' fails trying to build bfdver.texi - see attachment
> for log details
Summary of results:
Sources updated to 2022-12-31 at 13:42:04 UTC and all output dirs (obj,
release, dist, tools) were cleaned.
``build.sh tools'' fails trying to build bfdver.texi - see attachment
for log details
++--+--+
| Paul Goyette | PGP
12 matches
Mail list logo
