>> cc: error: no such file or directory:
>> '/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c'
>> cc: error: no input files
>> *** [ittnotify_static.pico] Error code 1
>
> 'make cleanworld' solved it, build without error.
> I used to always
On 2020-03-13 20:07, Waitman Gobble wrote:
On 2020-03-13 20:00, Dimitry Andric wrote:
On 13 Mar 2020, at 23:58, Waitman Gobble wrote:
On 2020-03-13 17:49, Waitman Gobble wrote:
On 2020-03-13 16:57, Bob Willcox wrote:
...
cc: error: no such file or directory:
Hi,
Since it is done in sample code, I have an option in the RPC-over-TLS
server daemon that does the SSL_CTX_set_client_CA_list() call.
When I test, I have not used this option and the code seems to work.
Maybe this is because the client only has a single certificate?
Here's the lame
On 2020-03-13 20:00, Dimitry Andric wrote:
On 13 Mar 2020, at 23:58, Waitman Gobble wrote:
On 2020-03-13 17:49, Waitman Gobble wrote:
On 2020-03-13 16:57, Bob Willcox wrote:
...
cc: error: no such file or directory:
On 13 Mar 2020, at 23:58, Waitman Gobble wrote:
>
> On 2020-03-13 17:49, Waitman Gobble wrote:
>> On 2020-03-13 16:57, Bob Willcox wrote:
...
>>> cc: error: no such file or directory:
>>> '/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c'
>>> cc: error: no
Bob Willcox bob at immure.com wrote on
Fri Mar 13 21:08:16 UTC 2020 :
> My 13.0-current system (just updated about 2 hours ago) that is failing with
> this
> error when trying to do a 'make makeworld'
>
> --- ittnotify_static.pico ---
> cc -target x86_64-unknown-freebsd13.0
>
On 2020-03-13 17:49, Waitman Gobble wrote:
On 2020-03-13 16:57, Bob Willcox wrote:
My 13.0-current system (just updated about 2 hours ago) that is
failing with this
error when trying to do a 'make makeworld'
--- ittnotify_static.pico ---
cc -target x86_64-unknown-freebsd13.0
On 2020-03-13 16:57, Bob Willcox wrote:
My 13.0-current system (just updated about 2 hours ago) that is
failing with this
error when trying to do a 'make makeworld'
--- ittnotify_static.pico ---
cc -target x86_64-unknown-freebsd13.0
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp
My 13.0-current system (just updated about 2 hours ago) that is failing with
this
error when trying to do a 'make makeworld'
--- ittnotify_static.pico ---
cc -target x86_64-unknown-freebsd13.0
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -fpic -DPIC
On Fri, Mar 13, 2020 at 01:04:42PM -0400, Ed Maste wrote:
> While looking at other things we came across ldconfig's a.out support,
> which hasn't been used by anything in the FreeBSD base system in ~2
> decades.
>
> I know there are (or at least recently were) folks using a.out
> binaries on
## Ian Lepore (i...@freebsd.org):
> And could its presence be indicated via sysctl in some way, so that
> ldconfig could do a.out hints only if support for them is available?
Less code, not more.
Regards,
Christoph
--
Spare Space
___
On Fri, 2020-03-13 at 13:34 -0400, Ed Maste wrote:
> On Fri, 13 Mar 2020 at 13:22, Ian Lepore wrote:
> >
> > Could a.out support be a kernel config option that's off by
> > default?
>
> Probably. That seems reasonable to me.
>
> > And could its presence be indicated via sysctl in some way, so
On Fri, 13 Mar 2020 at 13:22, Ian Lepore wrote:
>
> Could a.out support be a kernel config option that's off by default?
Probably. That seems reasonable to me.
> And could its presence be indicated via sysctl in some way, so that
> ldconfig could do a.out hints only if support for them is
On Fri, 2020-03-13 at 13:04 -0400, Ed Maste wrote:
> While looking at other things we came across ldconfig's a.out
> support,
> which hasn't been used by anything in the FreeBSD base system in ~2
> decades.
>
> I know there are (or at least recently were) folks using a.out
> binaries on
While looking at other things we came across ldconfig's a.out support,
which hasn't been used by anything in the FreeBSD base system in ~2
decades.
I know there are (or at least recently were) folks using a.out
binaries on contemporary FreeBSD. Most likely statically linked
proprietary software.
On Thu, Mar 12, 2020 at 11:11:53AM +0100, Michael Gmelin wrote:
>
>
> On Thu, 12 Mar 2020 10:31:40 +0100
> Alexander Leidinger wrote:
>
> > Hi,
> >
> > This command sets the keyboard layout. You are supposed to set the
> > keyboard layout which matches the physical layout of the hardware.
> >
16 matches
Mail list logo
