| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
* Replace ELK_USE_{X11,MOTIF} with ELK_GUI, which is either "none" or is
some combination of "xaw" and/or "motif".
* Reenable Motif -- it seems to build properly with OpenMotif-2.0.x.
* Modernize this package a bit and clean up how linker flags are passed to
the build process by using the new variables available.
|
|
|
|
flags for finding the X11 libraries. The value of X11_LDFLAGS is appended
to LDFLAGS if the packages uses X11.
|
|
understands "-Wl,-R" to be just "-R", so it will work fine.
|
|
the main transformations have been performed.
The ld wrapper can now accept "-Wl,*" arguments and transform them
appropriately by stripping of the -Wl and the commas. This will obiviate
the need for logic in pkgsrc that strips away the "-Wl," depending on
whether the platform was a.out or ELF, and whether the individual package
chose to link using "cc" or "ld".
|
|
one provided by bsd.pkg.mk when generating the PLIST from PERL5_PACKLIST.
|
|
|
|
|
|
|
|
|
|
by pthread.buildlink2.mk if the default one from the package's
buildlink2.mk suffices.
|
|
libraries.
|
|
depend on other uninstalled libtool archives. During the relinking process
the newly installed libraries weren't being found. We now insert the
appropriate -Ldir flags to allow them to be found in the uninstalled
locations.
|
|
|
|
${SH}. Enables rc.d script portability for non-NetBSD systems.
as discussed with jlam.
|
|
/etc/rc.d. This is controlled by the new variable PKG_RCD_SCRIPTS which
may be set in /etc/mk.conf or in the shell environment in which the
INSTALL script is executed. PKG_RCD_SCRIPTS only takes effect if
${PKG_CONFIG} == "YES" and defaults to NO.
|
|
RCD_SCRIPTS. From the comments in bsd.pkg.install.mk:
# rc.d scripts are automatically generated and installed into the rc.d
# scripts example directory at the post-install step. The following
# variables are relevent to this process:
#
# RCD_SCRIPTS lists the basenames of the rc.d scripts
#
# RCD_SCRIPT_SRC.<script> the source file for <script>; this will
# be run through FILES_SUBST to generate
# the rc.d script
#
# RCD_SCRIPTS_EXAMPLEDIR the directory in which to install the
# example rc.d scripts
#
# If the source rc.d script is not present, then the automatic handling
# doesn't occur.
|
|
|
|
exists, then use it as the default value of DEINSTALL_EXTRA_TMPL or
INSTALL_EXTRA_TMPL.
|
|
and can be turned of by "WGET_USE_SSL=NO".
|
|
Fixes ap-jk build breakage on Linux systems.
|
|
exceed any maximum length on values stored in a variable.
|
|
a system library so that we can prefer a system library to a pkgsrc one
when building with pkgsrc.
|
|
it may be used by buildlink2.
|
|
ordering them and using += instead of an accidental = . This should fix
pkg/18324 by John Kohl <jtk@kolvir.arlington.ma.us>.
|
|
bsd.buildlink2.mk. This allows packages that use buildlink2 to fix up
*-config and other shell scripts that hardcode wrong library names as a
side-effect of how buildlink2 works, e.g., the package thinks "-laa" works
because the wrapper silently converts it to "-laa-x11.
REPLACE_BUILDLINK files relative to ${WRKSRC}
REPLACE_BUIDLINK_PATTERNS shell glob
REPLACE_BUILDLINK_SED sed expression to run over the files named
above
|
|
buildlink2. We used to create a timestamp file in the .libs directory.
Now, we add a line to the *.la and *.lai file that directly notes that it
has been "modified by buildlink2". This makes it easier to debug problems
caused by using the wrong libtool during either a build or install by
checking if the *.la or *.lai files have the "modified by buildlink2" line.
|
|
catch arguments with symbols that are special to the shell.
|
|
* Slightly modify the way to prefix "xemacs-" to a package compiled for XEmacs.
* Suppress warnings issued when Emacs/XEmacs are not installed.
|
|
|
|
the shell would definitely interpret in a wrong fashion (like
"perl>=5.0" - we don't want to create some file).
Pointed out by Jan Schaumann <jschauma@netmeister.org> on tech-pkg.
|
|
shell quoting lossage.
|
|
location check within package Makefiles actually works as expected.
|
|
|
|
|
|
* Do the trick in mk/emacs.mk instead of each package's Makefile.
|
|
|
|
|
|
|
|
there.
|
|
|
|
dependency on ghostscript. This handles the dependency patterns that will
match either ghostscript{,-nox11} and ghostscript-gnu{,-nox11} depending
on which version number of ghostscript is required. From the comments at
the top of the file:
To use this Makefile fragment, simply:
(1) Optionally set GHOSTSCRIPT_REQD to the minimum version number of
Ghostscript required by the package,
(2) Optionally set USE_GHOSTSCRIPT to "build" to only add a build-time
dependency on Ghostscript,
(3) And include this Makefile fragment in the package Makefile,
|
|
CONFIGURE_DIRS, and allows running the shell commands in the do-build and
do-install targets within the specified directories. Both variables
default to ${WRKSRC}.
|
|
|
|
just -I and -L (modulo if LOCALBASE == /usr/local).
|
|
argument transform filter.
* Remove special ZOULARISBASE hack and use the new _BLNK_*PROTECT_SED
variables to accomplish the same thing.
|
|
${_PKGSRCDIR} and ${BUILDLINK_DIR} from any filtering, as they may be
subdirectories of ${LOCALBASE}, /usr/pkg, or /usr/local.
This should fix pkg/18142 and other puzzling problems reported on the
tech-pkg mailing list where it was necessary to revert back to buildlink1
versions of packages in order to build when the pkgsrc tree or the work
directories are kept under /usr/local.
|
|
buildlink2.mk file has it's own logic for how to add the perl dependency.
|
|
|
