summaryrefslogtreecommitdiffstats
path: root/lib/atf
Commit message (Collapse)AuthorAgeFilesLines
* Fix typo in lib/atf/libatfc++/Makefilengie2014-08-171-1/+1
| | | | | | | | | | LIBATFC should be LIBATF_C; this was missed in the initial import (r241823) PR: 192731 MFC after: 3 days Phabric: D619 Approved by: rpaulo (mentor)
* Homogenize libatf-* version numbers with upstream.jmmv2014-06-062-2/+2
| | | | | | | | | | | | The libatf-* major version numbers in FreeBSD were one version ahead of upstream because, when atf was first imported into FreeBSD, the upstream numbers were not respected. This is just confusing and bound to cause problems down the road. Fix this by taking advantage of the fact that libatf-* are now private and that atf is not yet built by default. However, and unfortunately, a clean build is needed for tests to continue working once "make delete-old-libs" has been run; hence the note in UPDATING.
* Change libatf-c and libatf-c++ to be private libraries.jmmv2014-05-254-34/+2
| | | | | | | | | | | | | | We should not be leaking these interfaces to the outside world given that it's much easier for third-party components to use the devel/atf package from ports. As a side-effect, we can also drop the ATF pkgconfig and aclocal files from the base system. Nothing in the base system needs these, and it was quite ugly to have to get them installed only so that a few ports could build. The offending ports have been fixed to depend on devel/atf explicitly. Reviewed by: bapt
* Use src.opts.mk in preference to bsd.own.mk except where we need stuffimp2014-05-063-1/+3
| | | | from the latter.
* Add atf m4 files from the vendor branch.jmmv2014-04-012-0/+6
| | | | | | | These were originally deleted as "not important" but, actually we need them in place if we want to be able to use autoconf on software that provides atf-based tests. (That includes being able to rebuild autotest from scratch on the Kyua cluster machines, as the automated setup does.)
* Make bsd.test.mk the only public mk fragment for the building of tests.jmmv2014-03-145-5/+5
| | | | | | | | | | | | | | Change {atf,plain,tap}.test.mk to be internal implementation details of bsd.test.mk. Makefiles that build tests should now only include bsd.test.mk and declaratively specify what they want to build, without worrying about the internal implementation of the mk files. The reason for this change is to permit building test programs of different interfaces from a single directory, which is something I had a need for while porting tests over from src/tools/regression/. Additionally, this change makes it possible to perform some other requested changes to bsd.test.mk in an easier manner. Coming soon.
* MFV: Import atf-0.20.jmmv2014-02-143-13/+19
|
* Generate and install pkg-config files for atf.jmmv2014-01-123-0/+45
| | | | | | | | | | These files are required to get packages in ports to build against atf and also to get a couple of currently-failing tests to pass. I'm following the approach already used by the libusb pkg-config files installed by the system regarding the location and the install rules. MFC after: 5 days
* Fix path to the process_helpers for the libatf-c++ tests.jmmv2014-01-101-0/+1
| | | | | | | | | | | Because we respect the FreeBSD src tree layout under /usr/tests, and because the layout of the tests in the atf distfile does not match the former, the tests for atf-c++ were not able to find the process_helper binary. Fix this by explicitly hardcoding the right path in the FreeBSD test suite. Obtained from: atf (git 1f0e878f7f127741a3762883ef24aef317e239d5) MFC after: 1 week
* Respect the original layout of the atf-{c,c++} tests.jmmv2014-01-106-39/+64
| | | | | | | | | Put test programs for internal modules into a 'detail' subdirectory of the libatf-c and libatf-c++ test directories, just as the upstream distribution does. This is necessary because the tests assume such layout to find the process_helper program, and currently fail because of this divergence. MFC after: 1 week
* To avoid having to explicitly test COMPILER_TYPE for settingdim2013-12-221-3/+1
| | | | | | | | | | | | | | | clang-specific or gcc-specific flags, introduce the following new variables for use in Makefiles: CFLAGS.clang CFLAGS.gcc CXXFLAGS.clang CXXFLAGS.gcc In bsd.sys.mk, these get appended to the regular CFLAGS or CXXFLAGS for the right compiler. MFC after: 1 week
* MFV: Import atf-0.18.jmmv2013-11-173-3/+4
| | | | Approved by: rpaulo (mentor)
* Fix the build of some ATF tests.jmmv2013-11-173-8/+8
| | | | | | | | | | | | | When building various programs from a single Makefile, program-specific variables are of the form <VAR>.<PROG>, not <VAR>_<PROG>. Fix this obvious typo to fix the build when WITH_TESTS=yes. I am not sure how this ever worked before given that manual inspection of bsd.progs.mk clearly shows that the expected character between the two components is a dot and not an underscore... but I suspect the changes in r258095 exposed this oddity. Approved by: rpaulo (mentor)
* Build and install the atf tests.jmmv2013-11-0810-5/+168
| | | | | Reviewed by: freebsd-testing Approved by: rpaulo (mentor)
* Remove -L<path> from LDADD, it doesn't belong there.marcel2012-11-071-1/+3
| | | | | | Add it to LDFLAGS instead. Submitted by: Garrett Cooper <yanegomi@gmail.com>
* Add ATF to the build. This is may be a bit rought around the egdes,marcel2012-10-224-0/+240
but committing it helps to get everyone on the same page and makes sure we make progress. Tinderbox breakages that are the result of this commit are entirely the committer's fault -- in other words: buildworld testing on amd64 only. Credits follow: Submitted by: Garrett Cooper <yanegomi@gmail.com> Sponsored by: Isilon Systems Based on work by: keramida@ Thanks to: gnn@, mdf@, mlaier@, sjg@ Special thanks to: keramida@
OpenPOWER on IntegriCloud