Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Oct 2017 20:56:38 -0300
From:      Joseph Mingrone <jrm@FreeBSD.org>
To:        Tijl Coosemans <tijl@FreeBSD.org>
Cc:        ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, portmgr@FreeBSD.org, Johannes M Dieterich <jmd@freebsd.org>, yuri@rawbw.com, maho@FreeBSD.org, sunpoet@FreeBSD.org
Subject:   Re: svn commit: r452962 - head/math/libRmath
Message-ID:  <861slmu8qx.fsf@phe.ftfl.ca>
In-Reply-To: <20171028182237.1f83708c@kalimero.tijl.coosemans.org> (Tijl Coosemans's message of "Sat, 28 Oct 2017 18:22:48 %2B0200")
References:  <201710270052.v9R0qf7A058644@repo.freebsd.org> <20171027125130.39e98c9c@kalimero.tijl.coosemans.org> <86d158vcve.fsf@phe.ftfl.ca> <20171028124843.56f8e8d3@kalimero.tijl.coosemans.org> <86y3nvtjlt.fsf@phe.ftfl.ca> <20171028182237.1f83708c@kalimero.tijl.coosemans.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-=
Content-Type: text/plain

Tijl Coosemans <tijl@FreeBSD.org> writes:
> It's not a gfortran problem.  It's a kernel or libthr problem.  You can
> work around it by avoiding the combination of recycled thread stacks and
> exception handling done by ports libgcc_s.  When you switched from curl
> to wget you avoided threads and that fixed the problem.  Switching to
> flang avoids ports libgcc_s and that also fixes the problem, but it's not
> necessary to go this way.  You could probably go back to curl if you
> build it with the CARES option instead of THREADED_RESOLVER.

I missed this paragraph last time around.

It's not really a switch to wget.  We just pull it in as RUN_DEPENDS
when gfortran is on.  R still defaults to downloading packages with
curl.  Users can create/edit configuration to switch to wget, which is
not a big deal, but not ideal.  I've copied sunpoet@, the maintainer of
ftp/curl.  sunpoet@, what do you think about switching ftp/curl's
default to c-ares instead of THREADED_RESOLVER to work around this
problem (until there are fixes for the threading problem that is
triggered with ports libgcc_s)?

Here is a quick-and-dirty poudriere testport run.  I say quick-and_dirty
because 1) I just included ports, which have a Makefile with
USES.*fortran in them, so there are probably some ports missing and 2) I
haven't looked in detail at the build logs to see what is going on.
math/lapack resulted in, by far, the most severe fallout.

http://pkg.awarnach.mathstat.dal.ca/build.html?mastername=11amd64-default&build=2017-10-28_12h15m47s

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAln1GTZfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1
QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW
755NYA/9G9qH5jKNM2cSVypyTbKQ/81hxJj/M8xsK5oH8mauUHrFNpuBVkYiZWqG
gApHrynCymIVbp3hDeQEjNtEfH/L9kX3eg4LLJLBon6VOEa1zigtiCvXRW1UGSad
Z6WX09dJVC5k+w0HVHnPES37K7nYdNwk5EGd7rnhRcY6A2hOnjYb1KR2EeoguINn
cixwaZHs8arVCsXFoZJ3HdjQ8zAhl+sANOf0bvicOMddQJbC3XsNUZeRQ8y+BKav
0U0YeAtwnrXYmX9XA7q6gxQRXKiNNZIdhK6fWvaL7sj7My+yUVcU9qX/7MYKDZsj
5udAQ12SmhrdcpKFae4wbHoghqqx+hOSyfYkIW61qGpPV0rutjPe1OHgGE5cOfKf
xMX4EqF1vy38ANrBMOPdoZpCFsdvH58/cQwgYrN3A8WCq/Tc49uDEiLt3l0tt1Wm
R3nfyeLz+UmTrroiKwXjkzLPkjeXO7v7Hg6dSf0JBFt+bnB01GDHT60TYdiVvGMF
kpNa4Sf7dSu3ND7r+pl0frOS1vZ2GnMFlb4Xl/pKpJCIwXzkhnMLhOVBMZEbmyPf
enpkBAnXmzPJgeqUViIaeIBOWNkLi/sMaxrMEoXMuTV/P8bsewha+NwtdB10OUhL
NCWctq82CnCXmFyZOsjzRUXAhdw3a5FMg/fN0juCzRH4TeKNa+4=
=40Lu
-----END PGP SIGNATURE-----
--=-=-=--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861slmu8qx.fsf>