Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Dec 2024 16:28:29 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 283301] lang/smlnj:  Update to 110.99.6.1
Message-ID:  <bug-283301-7788-xdQfdcjBEf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-283301-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-283301-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283301

--- Comment #3 from Johannes 5 <joemann@beefree.free.de> ---
> Unfortunately, compilation fails at the configure stage:
>=20
> Configuring asdl.
> [...]
> checking for gcc... gcc
> [...]
> configure:3575: gcc -O2 -pipe  -Wno-error=3Dincompatible-function-pointer=
-types -fPIC -fstack-protector-strong -fno-strict-aliasing    -fstack-prote=
ctor-strong  conftest.c  >&5
> cc1: error: '-Wno-error=3Dincompatible-function-pointer-types': no option=
 '-Wincompatible-function-pointer-types'; did you mean '-Wincompatible-poin=
ter-types'?
This should not happen when building the package with poudriere,
because in poudriere's clean jail no gcc would be hanging around.
But fortunately passing down CC=3D'${CC}' from the port's Makefile
to SML/NJ's own build procedure seems to help as well:

        <ftp://wrap7.free.de/pub/patch/smlnj.patch.20241215>;
        MD5 (smlnj.patch.20241215) =3D 0c5dfe976a2f41a73e9b8171331d3ac1

> Also, there is a warning from portlint, but you probably know.
If you have an idea how to avoid ${CHOWN}, please let me know.
As far as I can see, the warning is less annoying than having
stage-qa fail or trying to make USES=3Dshebangfix work during
the build phase of the port.

Thanks for your feedback and patience!
Johannes

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283301-7788-xdQfdcjBEf>