aboutsummaryrefslogtreecommitdiffstats
path: root/x11-wm
diff options
context:
space:
mode:
authorsobomax <sobomax@FreeBSD.org>2003-04-14 23:39:50 +0800
committersobomax <sobomax@FreeBSD.org>2003-04-14 23:39:50 +0800
commitd070da1db6fd9da4c41619e0e16586f43b638dee (patch)
treebe706de59b52876e8520ec570c89cc6840ebaa8a /x11-wm
parent617eb0f086a1ca89ada0ab03a30434507bd9bb55 (diff)
downloadfreebsd-ports-gnome-d070da1db6fd9da4c41619e0e16586f43b638dee.tar.gz
freebsd-ports-gnome-d070da1db6fd9da4c41619e0e16586f43b638dee.tar.zst
freebsd-ports-gnome-d070da1db6fd9da4c41619e0e16586f43b638dee.zip
Attempt to nail down strange problems people are reporting usially
around new release. Apparently, those problem steam from the fact that those users doesn't update their kernels along with userland, so that CONFIGURE_TARGET supplied by bsd.port.mk doesn't match OS version detected by configure script, making it believe that it is in the cross-compile environment. The same problem observed on bento. Use USE_REINPLACE while I'm here.
Diffstat (limited to 'x11-wm')
0 files changed, 0 insertions, 0 deletions