Summary: | devel/binutils: should provide a test/regression target | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Pedro F. Giffuni <pfg> | ||||
Component: | Individual Port(s) | Assignee: | Baptiste Daroussin <bapt> | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Only Me | CC: | arrowd, pfg | ||||
Priority: | --- | Keywords: | patch | ||||
Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(bapt) |
||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
The approach is wrong, all what is needed is a simple: TEST_TARGET=check Also note that to depend on dejagnu, TEST_DEPENDS=... should be enough. Btw the testsuite works here to the exception of some weird -Wa,-madd-bnd-prefix which clang does not accept The port does have test target now, although it fails for me with gcctestdir/ld: internal error in shndx, at ./symtab.h:170 c++: error: linker command failed with exit code 1 (use -v to see invocation) Anyways, can this be closed? Done ... |
Created attachment 174258 [details] Proof-of-concept patch Being such a critical third-party module we should have testing options for this port so we can catch regressions or evaluate better before enabling features. I borrowed the test option from the GCC port. I am not sure this adapts perfectly to binutils as the tests don't finish but it's a start.