On Fri, Aug 30, 2019 at 12:33:37AM -0400, Lawrence Teo wrote:
> On Wed, Aug 28, 2019 at 10:17:29PM -0400, Lawrence Teo wrote:
> > On Tue, Aug 27, 2019 at 10:52:52AM -, Christian Weisgerber wrote:
> > > On 2019-08-21, Stuart Henderson wrote:
> > >
> > > >> > * If you build ghidra on a system
On Wed, Aug 28, 2019 at 10:17:29PM -0400, Lawrence Teo wrote:
> On Tue, Aug 27, 2019 at 10:52:52AM -, Christian Weisgerber wrote:
> > On 2019-08-21, Stuart Henderson wrote:
> >
> > >> > * If you build ghidra on a system where gcc/g++/libstdc++ are
> > >> > available, it does indeed link
On Tue, Aug 27, 2019 at 10:52:52AM -, Christian Weisgerber wrote:
> On 2019-08-21, Stuart Henderson wrote:
>
> >> > * If you build ghidra on a system where gcc/g++/libstdc++ are
> >> > available, it does indeed link something against libstdc++ and
> >> > port-lib-depends-check indicates
On 2019-08-21, Stuart Henderson wrote:
>> > * If you build ghidra on a system where gcc/g++/libstdc++ are
>> > available, it does indeed link something against libstdc++ and
>> > port-lib-depends-check indicates WANTLIB+=stdc++.
>> >
>> > * If you build ghidra on a system where
On 2019/08/20 22:43, Lawrence Teo wrote:
> On Tue, Aug 20, 2019 at 04:32:48PM +0200, Christian Weisgerber wrote:
> > A few days ago, I did a test bulk build on amd64 with gcc, g++, and
> > libstdc++ removed from the system. Ports should not use these any
> > longer on clang platforms.
> >
> >
On Tue, Aug 20, 2019 at 04:32:48PM +0200, Christian Weisgerber wrote:
> A few days ago, I did a test bulk build on amd64 with gcc, g++, and
> libstdc++ removed from the system. Ports should not use these any
> longer on clang platforms.
>
> security/ghidra failed to build right away since it has
A few days ago, I did a test bulk build on amd64 with gcc, g++, and
libstdc++ removed from the system. Ports should not use these any
longer on clang platforms.
security/ghidra failed to build right away since it has stdc++ in
WANTLIB. Further testing shows:
* If you build ghidra on a system
