Re: [PING^7][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Sun, 26 Jan 2020, Jeff Law wrote: > > Ping for the build system parts of: > > > > > > > OK. Sorry for the terrible slowness on this kit. No worries, completely understood w

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

Hi Chung-Lin, > sorry for the late reply. No worries. > The 'AM_RUNTESTFLAGS = --tool_exec "$(CC)"' does work for us, but only > because you backed out the change > from libgomp-test-support.exp, and our installed testing doesn't use the > libgomp/testsuite/Makefile.* files > (we invoke runte

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

Hi Maciej, sorry for the late reply. On 2020/2/1 5:46 AM, Maciej W. Rozycki wrote: On Tue, 21 Jan 2020, Maciej W. Rozycki wrote: I'll give your proposal a shot and I'm lucky enough to have a build configuration where I can have no compiler preinstalled, so at least I can check if testing wit

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Tue, 21 Jan 2020, Maciej W. Rozycki wrote: > I'll give your proposal a shot and I'm lucky enough to have a build > configuration where I can have no compiler preinstalled, so at least I can > check if testing with your change applied correctly picks the newly built > uninstalled compiler in

Re: [PING^7][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Tue, 2020-01-21 at 02:19 +, Maciej W. Rozycki wrote: > On Fri, 20 Dec 2019, Mike Stump wrote: > > > > > This patch series addresses a problem with the testsuite compiler being > > > > set up across libatomic, libffi, libgo, libgomp with no correlation > > > > whatsoever to the target comp

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Tue, 14 Jan 2020, Chung-Lin Tang wrote: > Can you test if the attached patch works for you? The patch exports the build > sysroot > setting from the toplevel to target library subdirs, and adds the --sysroot= > option > when doing build-tree testing (I assume that blddir != "" test is suffici

[PING^7][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Fri, 20 Dec 2019, Mike Stump wrote: > >> This patch series addresses a problem with the testsuite compiler being > >> set up across libatomic, libffi, libgo, libgomp with no correlation > >> whatsoever to the target compiler being used in GCC compilation. > >> Consequently there in no arran

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

On 2020/1/6 11:25 PM, Maciej W. Rozycki wrote: Overall if libgomp-test-support.exp is considered appropriate for standalone testing, then I think two solutions are possible here: 1. An option is added to libgomp's $CC such that the compiler is able to make builds involving the offload comp

[PING^6][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Fri, 20 Dec 2019, Mike Stump wrote: > >> This patch series addresses a problem with the testsuite compiler being > >> set up across libatomic, libffi, libgo, libgomp with no correlation > >> whatsoever to the target compiler being used in GCC compilation. > >> Consequently there in no arran

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

Hi Maciej, On 1/6/20 4:25 PM, Maciej W. Rozycki wrote: Without the patch, the compiler is found (with [find_gcc] I suppose) and invoked as x86_64-none-linux-gnu-gcc. That works fine for us, but we do (I think) "installed testing", which IIUC is atypical. […] However before I make any definite

[PING^5][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Fri, 20 Dec 2019, Mike Stump wrote: > >> This patch series addresses a problem with the testsuite compiler being > >> set up across libatomic, libffi, libgo, libgomp with no correlation > >> whatsoever to the target compiler being used in GCC compilation. > >> Consequently there in no arran

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

Hi Julian, > FYI: This patch seems to be causing problems for our (internal -- as > you know!) test harness. I'm not sure if it's a local issue (or at least > something we can work around here), or a problem with the patch itself > though. I'm sorry to break your setup. I'm currently a little b

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

Hi Maciej, On Sun, 22 Dec 2019 00:43:54 + (GMT) "Maciej W. Rozycki" wrote: > On Fri, 20 Dec 2019, Mike Stump wrote: > > > >> This patch series addresses a problem with the testsuite > > >> compiler being set up across libatomic, libffi, libgo, libgomp > > >> with no correlation whatsoever t

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Fri, 20 Dec 2019, Mike Stump wrote: > >> This patch series addresses a problem with the testsuite compiler being > >> set up across libatomic, libffi, libgo, libgomp with no correlation > >> whatsoever to the target compiler being used in GCC compilation. > >> Consequently there in no arran

Re: [PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Dec 16, 2019, at 4:06 PM, Maciej W. Rozycki wrote: > > On Mon, 11 Nov 2019, Maciej W. Rozycki wrote: > >> This patch series addresses a problem with the testsuite compiler being >> set up across libatomic, libffi, libgo, libgomp with no correlation >> whatsoever to the target compiler being

[PING^4][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, 11 Nov 2019, Maciej W. Rozycki wrote: > This patch series addresses a problem with the testsuite compiler being > set up across libatomic, libffi, libgo, libgomp with no correlation > whatsoever to the target compiler being used in GCC compilation. > Consequently there in no arrangeme

[PING^3][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, 11 Nov 2019, Maciej W. Rozycki wrote: > This patch series addresses a problem with the testsuite compiler being > set up across libatomic, libffi, libgo, libgomp with no correlation > whatsoever to the target compiler being used in GCC compilation. > Consequently there in no arrangeme

[PING^2][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, 11 Nov 2019, Maciej W. Rozycki wrote: > This patch series addresses a problem with the testsuite compiler being > set up across libatomic, libffi, libgo, libgomp with no correlation > whatsoever to the target compiler being used in GCC compilation. > Consequently there in no arrangeme

[PING][PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, 11 Nov 2019, Maciej W. Rozycki wrote: > This patch series addresses a problem with the testsuite compiler being > set up across libatomic, libffi, libgo, libgomp with no correlation > whatsoever to the target compiler being used in GCC compilation. > Consequently there in no arrangeme

Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, Nov 11, 2019 at 10:44 AM Maciej W. Rozycki wrote: > > On Mon, 11 Nov 2019, Ian Lance Taylor wrote: > > > > Go's project doesn't take mail patches for changes. Please use gerrit ( > > > https://go-review.googlesource.com/ ). > > > > These patches are for gccgo, not the gc toolchain. They

Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, 11 Nov 2019, Ian Lance Taylor wrote: > > Go's project doesn't take mail patches for changes. Please use gerrit ( > > https://go-review.googlesource.com/ ). > > These patches are for gccgo, not the gc toolchain. They should > probably have been sent to gofrontend-dev rather than golang-d

Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, 11 Nov 2019, Ulderico Cirello wrote: > Go's project doesn't take mail patches for changes. Please use gerrit ( > https://go-review.googlesource.com/ ). Thanks for your reply; this is however too much effort for my limited resources and a one-off change. The reason is I'm not actively

Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, Nov 11, 2019 at 10:31 AM Kaz Kylheku (libffi) <382-725-6...@kylheku.com> wrote: > > On 2019-11-11 10:15, Ulderico Cirello wrote: > > Hi Maciej, > > > > Go's project doesn't take mail patches for changes. > > Is it that they'd have to read man pages and learn how to use common > utilities? >

Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot

On Mon, Nov 11, 2019 at 10:15 AM Ulderico Cirello wrote: > > Go's project doesn't take mail patches for changes. Please use gerrit ( > https://go-review.googlesource.com/ ). These patches are for gccgo, not the gc toolchain. They should probably have been sent to gofrontend-dev rather than gola

Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot

On 2019-11-11 10:15, Ulderico Cirello wrote: Hi Maciej, Go's project doesn't take mail patches for changes. Is it that they'd have to read man pages and learn how to use common utilities? Or that nobody has written a "patch in Go" yet?

[PATCH 0/4] Fix library testsuite compilation for build sysroot

Hi, This patch series addresses a problem with the testsuite compiler being set up across libatomic, libffi, libgo, libgomp with no correlation whatsoever to the target compiler being used in GCC compilation. Consequently there in no arrangement made to set up the compilation sysroot accordi

Re: [golang-dev] [PATCH 0/4] Fix library testsuite compilation for build sysroot

Hi Maciej, Go's project doesn't take mail patches for changes. Please use gerrit ( https://go-review.googlesource.com/ ). Thanks - ccf On Mon, Nov 11, 2019 at 10:12 AM Maciej W. Rozycki wrote: > Hi, > > This patch series addresses a problem with the testsuite compiler being >