Commit graph

11 commits

Author SHA1 Message Date
xtraeme
ee561b38da eww, replace another [ with ${TEST}. 2004-07-27 11:30:55 +00:00
xtraeme
5d398fabc4 s/echo/${ECHO}/ 2004-07-27 11:28:41 +00:00
wiz
0b38542de9 Do not use continuation -- line is short
enough, and this silences a pkglint warning.
2004-07-01 13:09:39 +00:00
xtraeme
38e875e52b Check for libpthread.so.* file with -f instead of echo as suggested by
grant, because previous check was not working fine, I tested it under
OpenBSD 3.5 and now just works.
2004-06-21 21:57:00 +00:00
xtraeme
b259186410 Under OpenBSD there is no libpthread.so, just libpthread.so.X.X, and
BUILDLINK_LDADD.pthread was empty, so add a check to find the libraries
and if they are found, add -lpthread to BUILDLINK_LDADD.pthread, thanks
to grant beattie for the suggestion.

Reported and tested by Sergio Jimenez <tripledes at eslack dot org>.
2004-06-21 00:06:37 +00:00
grant
c4e3c8cd15 when using native threads, only set BUILDLINK_CFLAGS.pthread=-pthread on
systems known to support its (FreeBSD, NetBSD, Linux).

fixes breakage caused by passing -pthread to SunPro cc(1) and likely
also fixes platforms other than the above.
2004-06-12 03:19:52 +00:00
seb
71f733521f revert previous. 2004-03-31 20:18:46 +00:00
seb
db7fd89879 When PTHREAD_TYPE is 'native' set USE_BUILTIN.pthread to YES and
add 'pthread' to BUILDLINK_PACKAGES so that
BUILDLINK_{{LD,C}FLAGS,LDADD}.pthread actually have an effect.

This should fix the build of at least tcl/tk related packages now
that tcl and tk packages are thread-aware.

Remove comments about linking native pthread libraries and headers into
${BUILDLINK_DIR} as this does not happen.
2004-03-29 15:16:58 +00:00
jlam
7db11b582a Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly
by moving the inclusion of buildlink3.mk files outside of the protected
region.  This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.

BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list.  This ordering property is used to check for builtin
packages in the correct order.  The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end.  However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 09:12:08 +00:00
jlam
0129c7eedd Append to BUILDLINK_DEPENDS.<pkg> instead of overriding it so that the
most restrictive dependency is always part of the DEPENDS/BUILD_DEPENDS
list.
2004-01-25 16:17:37 +00:00
jlam
339cd13cb2 Initial sprinkling of work-in-progress buildlink3.mk files for using the
buildlink3 framework.
2004-01-03 23:06:43 +00:00