The disabling gcc optimisation hacks is not needed anymore on 64bits archs.
This commit is contained in:
parent
d7291ba853
commit
45030a4f82
@ -1,4 +1,4 @@
|
||||
# $OpenBSD: Makefile,v 1.161 2012/03/31 18:27:35 ajacoutot Exp $
|
||||
# $OpenBSD: Makefile,v 1.162 2012/04/01 13:38:07 ajacoutot Exp $
|
||||
|
||||
COMMENT-main= general-purpose utility library
|
||||
COMMENT-docs= glib2 documentation
|
||||
@ -10,7 +10,7 @@ EXTRACT_SUFX= .tar.xz
|
||||
PKGNAME-main= glib2-${VERSION}
|
||||
PKGNAME-docs= glib2-docs-${VERSION}
|
||||
|
||||
REVISION-main= 1
|
||||
REVISION-main= 2
|
||||
|
||||
CATEGORIES= devel
|
||||
|
||||
@ -100,16 +100,6 @@ post-patch:
|
||||
.include <bsd.port.arch.mk>
|
||||
|
||||
pre-configure:
|
||||
# XXX
|
||||
# SIGSEGV on LP64_ARCHS at gclosure.c:290: i = closure->n_guards;
|
||||
# -> reproduce by adding a meeting|appointment under evolution into the
|
||||
# _local_ calendar for an already _passed_ date and running:
|
||||
# /usr/local/libexec/evolution/3.2/evolution-alarm-notify
|
||||
.if ${PROPERTIES:Mlp64}
|
||||
perl -pi -e 's,CFLAGS = \@CFLAGS\@,CFLAGS = \@CFLAGS\@ -O0,' \
|
||||
${WRKSRC}/gobject/Makefile.in
|
||||
.endif
|
||||
|
||||
perl -pi -e "s,/usr/local,${LOCALBASE},g;" \
|
||||
-e "s,/usr/share/locale,${LOCALBASE}/share/locale,g;" \
|
||||
-e "s,/usr/share/applications,${LOCALBASE}/share/applications,g;" \
|
||||
|
@ -1,4 +1,4 @@
|
||||
$OpenBSD: README-main,v 1.1 2012/01/01 09:00:46 ajacoutot Exp $
|
||||
$OpenBSD: README-main,v 1.2 2012/04/01 13:38:07 ajacoutot Exp $
|
||||
|
||||
+-----------------------------------------------------------------------
|
||||
| Running ${FULLPKGNAME} on OpenBSD
|
||||
@ -11,4 +11,4 @@ monitoring up to the open file descriptors limit.
|
||||
If gio-kqueue needs to handle large directories, the kern.maxfiles
|
||||
sysctl(8) should be increased by adding an entry in sysctl.conf(5) and
|
||||
the user's login(1) class modified accordingly by bumping the "cur" and
|
||||
"max" "openfiles" limit in login.conf(5).
|
||||
"max" openfiles limit in login.conf(5).
|
||||
|
Loading…
Reference in New Issue
Block a user