Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
From a discussion that took place offlist around
http://mail-index.netbsd.org/tech-pkg/2015/11/06/msg015926.html
Reviewed by gdt@
|
|
Reviewed by gdt@
|
|
Add pointer to a pkgsrc-bulk message about a 10.4 powerpc build, and
therefore drop notion that there are no 10.4 users.
|
|
Switch to using arch(1) to detect the architecture of host
Set $machine_arch to x86_64 if on amd64
Pass $machine_arch to the devel/bmake build process
Reviewed by wiz@
|
|
Switch $machine_arch to x86_64 if on OpenBSD/amd64
Pass $machine_arch to the devel/bmake build process
Reviewed by wiz@
|
|
Replace and simplify the versions section. Drop notion of
supported/deprecated. Explain why people run specific old versions.
Assert that there are no 10.4 pkgsrc users, and very few 10.5. Keep
notion that PRs for <= 10.5 without fixes can be closed without
fixing.
Explain Darwin vs OS X. Point to PureDarwin. Explain that pkgsrc for
Darwin is really for OSX and invite doc patches.
Make a few minor edits.
It remains for someone to explain more clearly the issue of
broken/missing SDKs in 10.11 and command line tools.
As discussed on tech-pkg, with input from jperkin and tron.
|
|
Thanks to wiz@ and Luis Muir for pointing these out.
|
|
- Remove information about older versions of pkgsrc.
- Note that /usr/include is gone and that there are SDKs
- Add hazy explanation of the missing SDK/command-line-tools issue.
- Add 10.11 (but do not change deprecation status of anything).
- Clarify (but do not try to update for current reality) the 10.6/10.9
bulk build descriptions.
|
|
"pdksh" package. Using the package is too problematic, see PR pkg/39524.
|
|
Initial patchset to add support by rodent@
Further adjustments made based on feedback by joerg@
Tested by myself with numerous bulkbuilds thanks to Patrick Wildt @ Bitrig
Reviewed by bsiegert@ joerg@ wiz@
|
|
successfully using the stock /bin/sh supplied with the system, things don't work
correctly.
Reviewed by wiz@
|
|
|
|
GCC and X11_TYPE=modular is what will work best.
|
|
|
|
|
|
This was added in 2004 and there have been no reports of anyone even
trying to use it in many many years. Searching on the web finds only
information from 2003.
|
|
Add Joyent bulk build links.
CVS: ----------------------------------------------------------------------
CVS: CVSROOT cvs.NetBSD.org:/cvsroot
CVS: please use "PR category/123" to have the commitmsg appended to PR 123
|
|
|
|
as a build dependency as needed.
|
|
|
|
appropriate. The default continues to be 1.
|
|
User/group names are used instead of uid/gid.
Problem with spaces inside user/group name should be fixed by Cygwin
support added some time ago.
|
|
|
|
|
|
looking sufficiently like gcc. Inspect "cc" instead, and don't
believe it's __GNUC__ unless it's also not __clang__.
While here, if you manage to find and install PackageMaker.app, it
still works on 10.9 for --binary-macpkg.
From Sevan Janiyan.
|
|
|
|
includes gcc which is actually clang.
|
|
|
|
when bootstrapping bmake.
|
|
to devel/bmake when bootstrapping the latter.
bmake doesn't take this environment variable into consideration anyway.
|
|
exists.
It is expected in mk/compiler/clang.mk that CLANGBASE is set properly
even if builtin clang is selected.
|
|
Basically: 10.9's sed is broken, bootstrap works around this via nbsed
on 10.9, and therefore while a 10.6 boostrap's binaries will *run* on
10.9, one can't reliably build new packages.
(Thanks to jperkin@ for pointing this out.)
|
|
|
|
|
|
The license donation for OpenServer 5.0.7/3.2 by Xinuos Inc. helped to
make this commit possible.
|
|
Explain clang. Add 10.9. Point out jperkin's builds.
|
|
This fixes bootstrapping on FreeBSD 10 where cc is Clang
pretending poorly to be GCC.
|
|
building 32-bit packages on x86_64 is supported.
|
|
|
|
|
|
Don't insist on moving system tools.
|
|
missing the bit.
|
|
|
|
instead of install-sh on platforms which need a BSD install. The install-sh
script is still used during the bootstrap process regardless.
Default to 'yes' on SunOS. Other platforms can migrate over once they confirm
that sysutils/bsdinstall builds correctly.
|
|
|
|
|
|
|
|
|
|
|