Summary: | [TEST] net-libs/libaxc-0.3.4-r2 - mv: cannot stat *.g*: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Sebastian Pipping <sping> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | TESTFAILURE |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/gkdr/axc/issues/26 | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=814125 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 732706 | ||
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tar.bz2 net-libs:libaxc-0.3.4-r2:20210722-081927.log temp.tar.bz2 |
Description
Toralf Förster
2021-07-22 08:50:10 UTC
Created attachment 725692 [details]
emerge-info.txt
Created attachment 725695 [details]
emerge-history.txt
Created attachment 725698 [details]
environment
Created attachment 725701 [details]
etc.portage.tar.bz2
Created attachment 725704 [details]
net-libs:libaxc-0.3.4-r2:20210722-081927.log
Created attachment 725707 [details]
temp.tar.bz2
Hi Toralf, what is "cc" in this environment? For me it's GCC 9.3.0 and over here it does put some *.g* files to move into the current working directory. When I add -v to the mv call (at two places) I get this output: [..] mv -v *.g* test renamed 'axc_crypto.gcda' -> 'test/axc_crypto.gcda' renamed 'axc_crypto.gcno' -> 'test/axc_crypto.gcno' renamed 'test_store.gcda' -> 'test/test_store.gcda' renamed 'test_store.gcno' -> 'test/test_store.gcno' [..] mv -v *.g* test renamed 'axc_crypto.gcda' -> 'test/axc_crypto.gcda' renamed 'axc_crypto.gcno' -> 'test/axc_crypto.gcno' renamed 'test_client.gcda' -> 'test/test_client.gcda' renamed 'test_client.gcno' -> 'test/test_client.gcno' [..] Any ideas why these files are not generated in your environment? Thanks and best, Sebastian (In reply to Sebastian Pipping from comment #7) > Hi Toralf, > > what is "cc" in this environment? The tinderbox updates GCC at the beginning to ~æmd64, in this case as seen in attached emerge-history..txt: 2021-07-15T12:47:12 >>> sys-devel/gcc-11.1.0-r2 2021-07-15T14:13:00 <<< sys-devel/gcc-10.3.0-r1 I have tried with GCC 11 now which is putting the *.g* files straight into the test/ folder and hence there is nothing to move. Okay! Reported upstream now The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=33fa09b0dc127aba68a045f84032ed2fd1811cd2 commit 33fa09b0dc127aba68a045f84032ed2fd1811cd2 Author: Sebastian Pipping <sping@gentoo.org> AuthorDate: 2021-08-22 23:07:45 +0000 Commit: Sebastian Pipping <sping@gentoo.org> CommitDate: 2021-08-22 23:09:22 +0000 net-libs/libaxc: 0.3.5 + GCC 11 test fix Closes: https://bugs.gentoo.org/803353 Signed-off-by: Sebastian Pipping <sping@gentoo.org> Package-Manager: Portage-3.0.22, Repoman-3.0.3 net-libs/libaxc/Manifest | 1 + net-libs/libaxc/libaxc-0.3.5.ebuild | 62 +++++++++++++++++++++++++++++++++++++ 2 files changed, 63 insertions(+) |