|
From: Bart V. A. <bar...@gm...> - 2009-01-14 07:20:24
|
On Tue, Jan 13, 2009 at 11:57 PM, Nicholas Nethercote <n.n...@gm...> wrote: > On Tue, Jan 13, 2009 at 8:18 PM, Bart Van Assche > <bar...@gm...> wrote: >> On Tue, Jan 13, 2009 at 5:25 AM, <sv...@va...> wrote: >>> Modified: branches/DARWIN/memcheck/tests/linux/Makefile.am >>> =================================================================== >>> --- branches/DARWIN/memcheck/tests/linux/Makefile.am 2009-01-13 03:32:52 UTC (rev 8943) >>> +++ branches/DARWIN/memcheck/tests/linux/Makefile.am 2009-01-13 04:25:04 UTC (rev 8944) >>> @@ -1,12 +1,12 @@ >>> noinst_SCRIPTS = filter_stderr >>> >>> EXTRA_DIST = $(noinst_SCRIPTS) \ >>> - linux-capget linux-capget.stderr.exp \ >>> - linux-timerfd-syscall linux-timerfd-syscall.stderr.exp >>> + capget capget.stderr.exp \ >>> + timerfd-syscall timerfd-syscall.stderr.exp >>> >>> check_PROGRAMS = \ >>> - linux-capget \ >>> - linux-timerfd-syscall >>> + capget \ >>> + timerfd-syscall >>> >>> AM_CPPFLAGS = -I$(top_srcdir)/include >>> AM_CFLAGS = $(WERROR) @FLAG_M32@ -Winline -Wall -Wshadow -g \ >>> >>> [ ... ] >> >> Hello Nicholas, >> >> Are you aware that autoconf/automake supports conditional compilation >> ? You can find an example in drd/tests/Makefile.am, e.g. in the >> following lines: >> >> if HAVE_BOOST_1_35 >> check_PROGRAMS += boost_thread >> endif > > Yes, it's used in lots of our Makefile.am files. But what is the > relevance for this file? Sorry, I didn't look closely enough to the diff. I do not understand why linux-timerfd-syscall.* was renamed into timerfd-syscall.*. AFAIK the timerfd system call only exists in Linux and not in other kernels (FreeBSD, Darwin) ? Bart. |