tv
4b5d899ef8
Revert previous (re-add common CPP_PRECOMP_FLAGS). For consistency, also
...
move usage of _USER_DEPENDS and _OPSYS_MAX_CMDLEN to bsd.pkg.mk.
2004-11-16 18:04:00 +00:00
tv
2e3f2421db
CPP_PRECOMP_FLAGS is a Darwinism only. Move its frobbing of CPPFLAGS to
...
platform/Darwin.mk (simplification).
2004-11-16 16:21:40 +00:00
tv
2e2cb6b1ef
Clarify previous (missing a word).
2004-10-29 15:15:50 +00:00
tv
6e04a29aad
Add a block comment to track the base addresses of Interix shlibs as used
...
in pkgsrc. (Since they are non-PIC, they require better than just default
base addresses in some fashion, or else face runtime text relocation.)
2004-10-29 15:15:10 +00:00
tv
ce5ae8b6ad
Collapse ROOT_CMD a little; it's possible to make all invocations do the
...
$(id -un ...) dance for canonical naming.
2004-10-29 14:53:39 +00:00
tv
9a8ac08ae7
Use /bin/test. The /bin/sh builtin has some bugs with symlinks.
2004-10-13 17:50:01 +00:00
tv
53860a0446
Make strip/no-strip choice more consistent:
...
Move check for INSTALL_UNSTRIPPED to the platform/*.mk files, alongside
existing check for DEBUG_FLAGS.
2004-10-13 15:31:31 +00:00
tv
9e2ecafeae
Another Interix fubar workaround: C++ libs weren't linking in libtool
...
because Interix installs completely hosed .la files for libstdc++ and
libsupc++. Make libtool instead trust g++ to DTRT.
2004-10-12 04:41:39 +00:00
tv
c12846d533
Make -export-symbols work properly under Interix. (The Interix ld(1) does
...
not implicitly add `_' to -retain-symbols-file values, so we have to add
it manually before doing the physical link.)
2004-10-11 16:51:56 +00:00
tv
26bca1504d
Add a comment explaining that bizarre $$(id -un ...) construct in ROOT_CMD.
2004-10-09 04:12:58 +00:00
tv
61fabf5361
Move -D_ALL_SOURCE for Interix, required for nearly every compilation, from
...
the funky CPPFLAGS assignment into the new wrapper framework.
2004-10-09 03:49:13 +00:00
jlam
dffc19378a
Reorganize some of the files under pkgsrc/mk:
...
(1) defs.${OPSYS}.mk --> platform/${OPSYS}.mk.
The "platform" subdirectory is where all of the ${OPSYS}-specific
infrastructure logic should reside.
(2) bsd.pkg.defaults.mk --> defaults/mk.conf
bsd.pkg.obsolete.mk --> defaults/obsolete.mk
Renaming bsd.pkg.defaults.mk to defaults/mk.conf is to mimic the way
that NetBSD has /etc/rc.conf as well as /etc/defaults/rc.conf, where
the latter is a full list of user-settable variables, and the two
files share the same name to reinforce the fact /etc/defaults/rc.conf
can be directly copied in place as /etc/rc.conf. This is the same
relationship shared by defaults/mk.conf and /etc/mk.conf.
2004-10-06 20:51:47 +00:00
