On Fri, 6 Dec 2024, Thomas Schwinge wrote:
> First: Tom, what was your original intention why we'd keep the generated
> files in the sources? (..., instead of just generating them at build
> time, like 'gcc/config/nvptx/t-omp-device' does for
> 'omp-device-properties-nvptx', for example. In that
Thomas Schwinge writes:
> Hi Sam and Tom!
Hi!
>
> On 2024-12-06T09:13:40+, Sam James wrote:
>> Providing parameters to `.` when sourcing is a bashism and not supported
>> by POSIX shell which causes a build failure when compiling a toolchain
>> for nvptx-none with dash as /bin/sh.
>
> Hmm,
Hi Sam and Tom!
On 2024-12-06T09:13:40+, Sam James wrote:
> Providing parameters to `.` when sourcing is a bashism and not supported
> by POSIX shell which causes a build failure when compiling a toolchain
> for nvptx-none with dash as /bin/sh.
Hmm, something must be wrong in that statement,
Providing parameters to `.` when sourcing is a bashism and not supported
by POSIX shell which causes a build failure when compiling a toolchain
for nvptx-none with dash as /bin/sh.
gen-copyright.sh takes a parameter for the format of copyright notice
required. Switch that to using an environment v
