On Sat, 21 Oct 2023, Manuel Bouyer wrote:
> What's strange is that I did a full build on HEAD and didn't notice
> the issue.
As did I. Building HEAD with the change worked just fine, but once it
was pulled up to netbsd-10, the XEN3{,PAE}_DOM0 kernels fail as previously
described.
> Will look
On Sat, Oct 21, 2023 at 11:46:48AM +0200, Manuel Bouyer wrote:
> On Fri, Oct 20, 2023 at 06:47:54PM -0500, John D. Baker wrote:
> > On Thu, 19 Oct 2023, Manuel Bouyer wrote:
> >
> > > On Thu, Oct 19, 2023 at 08:46:27AM -0500, John D. Baker wrote:
> > >
> > > > [...]
> > > > # link
On Fri, Oct 20, 2023 at 06:47:54PM -0500, John D. Baker wrote:
> On Thu, 19 Oct 2023, Manuel Bouyer wrote:
>
> > On Thu, Oct 19, 2023 at 08:46:27AM -0500, John D. Baker wrote:
> >
> > > [...]
> > > # link VERTHANDI/netbsd
> > > /r0/build/netbsd-10/tools/amd64/bin/i486--netbsdelf-ld -Map
On Fri, 20 Oct 2023, John D. Baker wrote:
> Thanks! HEAD built just fine, but with -10/i386, my custom kernels build
> OK, but the stock XEN3PAE_DOM0 build fails with:
>
> [...]
> # link XEN3PAE_DOM0/netbsd
> /r0/build/netbsd-10/tools/amd64/bin/i486--netbsdelf-ld -Map netbsd.map --cref
>
On Thu, 19 Oct 2023, Manuel Bouyer wrote:
> On Thu, Oct 19, 2023 at 08:46:27AM -0500, John D. Baker wrote:
>
> > [...]
> > # link VERTHANDI/netbsd
> > /r0/build/netbsd-10/tools/amd64/bin/i486--netbsdelf-ld -Map netbsd.map
> > --cref -T netbsd.ldscript -Ttext c010 -e start -X -o netbsd
On Thu, Oct 19, 2023 at 08:46:27AM -0500, John D. Baker wrote:
> The following change in -current:
>
> https://mail-index.netbsd.org/source-changes/2023/10/16/msg148163.html
>
> and its subsequent pull-up to netbsd-10:
>
>
The following change in -current:
https://mail-index.netbsd.org/source-changes/2023/10/16/msg148163.html
and its subsequent pull-up to netbsd-10:
https://mail-index.netbsd.org/source-changes/2023/10/18/msg148226.html
breaks building kernels which exclude "genfb". The failure is as