*ping* [PATCH] Fix generation of tree-check.h during release build

Jan-Benedict Glaw <[email protected]>
Newsgroups gmane.os.netbsd.current
Message-ID <[email protected]>
Hi!

On Mon, 2025-10-13 09:38:08 +0200, Jan-Benedict Glaw <[email protected]> wrote:
> On Sat, 2025-10-11 05:28:07 +1100, matthew green <[email protected]> wrote:
> > i commited the basic_file.cc fix.  thanks!
> > 
> > the tree-check.h one is odd.  it *should* be created before anything
> > else in usr.bin/backend:
> > 
> > DPSRCS+=        insn-attr.h insn-codes.h insn-config.h insn-flags.h tree-check.h
> > 
> > so i'm not sure what's happening here right now.
> 
> 
> This was my first shot and it made it build (cf.
> http://toolchain.lug-owl.de/laminar/log/netbsd-vax-vax/181):
> 
> diff --git a/external/gpl3/gcc/usr.bin/backend/Makefile b/external/gpl3/gcc/usr.bin/backend/Makefile
> index 0600531f3b67..16aaf9af6b0c 100644
> --- a/external/gpl3/gcc/usr.bin/backend/Makefile
> +++ b/external/gpl3/gcc/usr.bin/backend/Makefile
> @@ -498,7 +498,7 @@ gtype-desc.h: rs6000-builtins.h
>  aarch64-builtins.o: aarch64-builtin-iterators.h
>  tm.h: insn-constants.h
>  genextract.lo: insn-config.h
> -gencondmd.lo: tm_p.h tm-constrs.h
> +gencondmd.lo: tm_p.h tm-constrs.h tree-check.h
>  read-rtl.lo gencodes.lo genattrtab.lo genautomata.lo: tm.h gtype-desc.h
>  genattr-common.lo gensupport.lo genconditions.lo gentarget-def.lo: tm.h
>  genattr.lo genflags.lo genemit.lo genconfig.lo gencheck.lo: gtype-desc.h tm.h
> 
> 
> However, I'm not too sure if that's actually The Right Thing To Do.

*ping*   Anybody experiencing a similiar issue (building on
Linux/amd64 for NetBSD/VAX)?  Any comment on the patch?

Thanks,
  Jan-Benedict

--
signature.asc (application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCaO+TVQAKCRAdvV51g5nh
u2aSAJ43sxZEahB2nGhh+F7hGMhw7WQhTACfVmx/1y1HBNva+Ta3gTrtVqiIJnk=
=vw7f
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.