Re: Clang Import Breakage

2019-03-24 Thread Konstantin Belousov
On Sun, Mar 24, 2019 at 07:03:11AM +0100, Jan Beich wrote: > Sean Bruno writes: > > > On 3/23/19 5:57 PM, Dimitry Andric wrote: > >> This is fallout of , > >> which enabled --no-allow-shlib-undefined by default. See also > >>

Re: Clang Import Breakage

2019-03-24 Thread Jan Beich
Sean Bruno writes: > On 3/23/19 5:57 PM, Dimitry Andric wrote: >> This is fallout of , >> which enabled --no-allow-shlib-undefined by default. See also >> . Executive summary: lots of programs >> do not specify a

Re: Clang Import Breakage

2019-03-23 Thread Sean Bruno
On 3/23/19 5:57 PM, Dimitry Andric wrote: > This is fallout of , > which enabled --no-allow-shlib-undefined by default. See also > . Executive summary: lots of programs > do not specify all their required librari

Re: Clang Import Breakage

2019-03-23 Thread Dimitry Andric
On 24 Mar 2019, at 00:22, Sean Bruno wrote: > > audio/shout-idjc seems to have broken in a new and exciting way after > the 8.0 import. > > It would appear that the ports infrastructure detects libssl and libogg > exist (if the beginning of my logs are to be believed) but then are not > used dur

Clang Import Breakage

2019-03-23 Thread Sean Bruno
audio/shout-idjc seems to have broken in a new and exciting way after the 8.0 import. It would appear that the ports infrastructure detects libssl and libogg exist (if the beginning of my logs are to be believed) but then are not used during libtool/LD stages later on resulting in missing symbols.