Date: Mon, 04 Nov 2019 20:09:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241710] please increase ARG_MAX Message-ID: <bug-241710-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241710 Bug ID: 241710 Summary: please increase ARG_MAX Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: thierry@FreeBSD.org [See also the closed PR 208154] I'm trying to upgrade the port french/aster to the latest stable release. This is a complex port: it has no Makefile (in the upstream tarball, but of course there is a Makefile for the port), and it uses a combination of setup.py (Python) and a bundled waf. At this point, it builds, but the latest step (linkage) fails with the following message: gfortran9: fatal error: cannot execute '/usr/local/libexec/gcc9/gcc/x86_64-portbld-freebsd12.0/9.2.0/collect2': execv: Argument list too long Yes, linkage is done by gfortran, in a classical way: gfortran9 (some -Wl parameters) (a very long list of object files .o) (a list of several libraies with their paths) but the problem is not caused neither by gfortran nor by the final linker: if I execute the same command line manually from my shell, it succeeds and the aster program is built. So I guess that the problem is caused partly by the arguments list, but also by the environment variables brought by the build system. On my machine, `getconf ARG_MAX' returns 262144. There's a sysctl kern.argmax, but it's read-only and initialized to ARG_MAX. On PR 208154, for the same problem with Libreoffice, a work-around was to disable-mergelibs. I'll try to apply the same with Code_Aster, but it's not that easy with their build system (no configure). Anyway, it would be a good thing to increase this limit, as other OSes do. --=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-241710-227>