On Mon, 28 May 2018 17:37+0200, Christoph Moench-Tegeder wrote:
> (I'm not only "not a synth user", but also "rather inept with Ada").
I started learning Ada this year because of synth, and I'm barely a
novice Ada programmer. :-)
--
Trond.
___
## Trond Endrestøl (trond.endres...@fagskolen.gjovik.no):
> The latest commits to the synth repo forces synth to copy /etc/rc.subr
> and /etc/rc.d/ldconfig into each chroot.
Aha!
Yes, looking at
https://github.com/jrmarino/synth/commit/465ab8d2133a9d1e15cbf46337a1a809f828495d
I think the issue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #19 from Eitan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367
Eugene Grosbein changed:
What|Removed |Added
CC||eu...@freebsd.org
There's discussion about nss-related linking failures in other ports:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228540
and the common denominator in there cases is synth (there are no problems
in poudriere). Over there, Trond had the idea that this might be related
to
On Mon, 28 May 2018 13:44+0200, Christoph Moench-Tegeder wrote:
> has synth some special "optimization" for handling ldconfig?
Looking at src/replicant.adb of synth, I see it runs ldconfig when
setting up each chroot env using this procedure:
-- execute_ldconfig
On Mon, 28 May 2018 15:24+0200, Trond Endrestøl wrote:
> I can see one reason for not making /etc/rc.subr accessible inside
> each chroot, and thus a copy of the ldconfig startup script, and that
> is to prevent services from being started automatically within each
> chroot.
The latest
