Module Name:src
Committed By: riastradh
Date: Fri Nov 22 03:22:12 UTC 2024
Removed Files:
src/external/bsd/atf/lib/libatf-c++: atf-c++.expsym
Log Message:
libatf-c++: Nix expsym for now.
Evidently this is machine-dependent owing to variation in C++ symbols
across ABIs:
-
Module Name:src
Committed By: riastradh
Date: Fri Nov 22 03:22:12 UTC 2024
Removed Files:
src/external/bsd/atf/lib/libatf-c++: atf-c++.expsym
Log Message:
libatf-c++: Nix expsym for now.
Evidently this is machine-dependent owing to variation in C++ symbols
across ABIs:
-
On Sun, Jul 15, 2012 at 12:05:51AM +, David Brownlee wrote:
> Modified Files:
> src/external/bsd/atf/lib/libatf-c++: Makefile
>
> Log Message:
> Check for ${HAVE_GCC} and pick the right path to stdc++
Shouldn't these paths be provided by bsd.lib.mk, as the installed ones
are by bsd.
On Thu, Jul 12, 2012 at 12:15 PM, Christos Zoulas wrote:
> Module Name:src
> Committed By: christos
> Date: Thu Jul 12 16:15:40 UTC 2012
>
> Modified Files:
> src/external/bsd/atf/lib/libatf-c++: Makefile
>
> Log Message:
> Properly include dependent library, unbreaks objdi
On Jul 12, 3:30pm, j...@netbsd.org (Julio Merino) wrote:
-- Subject: Re: CVS commit: src/external/bsd/atf/lib/libatf-c++
| Does bsd.test.mk need a similar change? It's also using DPADD.
No, bsd.test.mk is using the installed versions of the libraries.
You need to depend on the build ver
