Re: Build failed compiling ittnotify_static.pico
Dimitry Andric wrote:
> On 14 Mar 2020, at 17:24, Roman Bogorodskiy wrote:
> >
> > 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:
> > '/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c'
> > cc: error: no input files
> > *** [ittnotify_static.pico] Error code 1
> > Anyone else seeing this? Any suggestions for a fix?
> > Thanks,
> > Bob
> I've been getting the same thing since yesterday. I think the file is
> actually
> ittnotify_static.cpp
> >>>
> >>>
> >>> This is supposed to handle the rename, for some reason it's not happening
> >>> on my machine.
> >>>
> >>> Makefile.inc1
> >>>
> >>> # 20200310 r358851 rename of openmp's ittnotify_static.c to .cpp
> >>> .for f in ittnotify_static
> >>> @if [ -e "${OBJTOP}/lib/libomp/.depend.${f}.pico" ] && \
> >>> egrep -qw '${f}\.c' ${OBJTOP}/lib/libomp/.depend.${f}.pico;
> >>> then \
> >>> echo "Removing stale dependencies for ${f}"; \
> >>> rm -f ${OBJTOP}/lib/libomp/.depend.${f}.* \
> >>> ${OBJTOP}/obj-lib32/lib/libomp/.depend.${f}.* \
> >>>
> >>> ${LIBCOMPAT:D${LIBCOMPAT_OBJTOP}/lib/libomp/.depend.${f}.*}; \
> >>> fi
> >>> .endfor
> >>
> >> Hm, so during your buildworld, does it show "Removing stale dependencies
> >> for ittnotify_static" or not? And is the .depend file there? Can you
> >> check /usr/obj for the file .depend.ittnotify_static.pico, and list its
> >> permissions?
> >>
> >> -Dimitry
> >>
> >
> > I have the same issue updating one of my poudriere jails.
> > I don't see "Removing stale dependencies ..." messages.
> >
> > I see a couple of ittnotify_static related messages:
> >
> > make[5]:
> > /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/obj-lib32/lib/libomp/.depend.ittnotify_static.pico,
> > 43: ignoring stale .depend for
> > /workspace/poudriere/jails/current/usr/src/contrib/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c
> > ...
> > make[5]:
> > /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/obj-lib32/lib/libomp/.depend.ittnotify_static.pico,
> > 43: ignoring stale .depend for
> > /workspace/poudriere/jails/current/usr/src/contrib/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.h
>
> These are for the 32-bit stage. The initial fix I committed in r358907
> worked for the main buildword stage, but apparently not for the 32-bit
> stage, which stores its object files in a slightly different directory
> (e.g. the obj-lib32 subpath).
>
> Ed Maste tried to fix that up in r358909, but maybe it does not work in
> all situations, for example with custom MAKEOBJDIRPREFIX settings?
>
>
> > $ ls -al
> > /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico
> > -rw-r--r-- 1 root wheel 6565 Mar 14 19:30
> > /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico
>
> What is in the first two lines of that file?
$ head -2
/usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico
ittnotify_static.pico: \
/workspace/poudriere/jails/current/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.cpp
\
$
> -Dimitry
>
Roman Bogorodskiy
signature.asc
Description: PGP signature
Re: when does a server need to use SSL_CTX_set_client_CA_list()?
Garrett Wollman wrote: >Rick Macklem writes: >>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? > >In general, the server needs to send a list of CAs that it's willing >to accept for client certificate use, because the server should never >accept just any old CA; normally, a client will interpret receiving >the list as a request to send a client certificate issued by one of >the indicated CAs, but the client can send its certificate even if the >server doesn't send the list or even if the server sends a list but >client certificate isn't issued by a CA on the list. > >It's probably a good idea to send the list even if there's only a >single valid CA, configured by prior agreement; the overhead is >minimal and it gives an indication to a fussy or confused client what >is being required of it. Ok, so does SSL_CTX_load_verify_locations() set up the server to verify the certificates and SSL_CTX_set_client_CA_list() set the list of certificate names sent to the client? Put another way, should the server normally: SSL_CTX_load_verify_locations(ctx, cafile, NULL); and SSL_CTX_set_client_CA_list(SSL_CTX_load_client_CA_file(cafile)); where cafile is the file with the CA certificates in it? I currently have the server setting these via separate options and only do the first one. If they both use the same file, then I can simplify things and get rid of one of the options. Thanks for your help with this, rick >My recollection is that in the OpenSSL API in particular, if you don't >set an explicit client CA list, but you *do* set a CA bundle or >directory to automatically construct the *server's* trust path, then >the library will just send the name of every single CA it knows about. -GAWollman ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Build failed compiling ittnotify_static.pico
On Sat, 14 Mar 2020 at 13:14, Dimitry Andric wrote: > > These are for the 32-bit stage. The initial fix I committed in r358907 > worked for the main buildword stage, but apparently not for the 32-bit > stage, which stores its object files in a slightly different directory > (e.g. the obj-lib32 subpath). > > Ed Maste tried to fix that up in r358909, but maybe it does not work in > all situations, for example with custom MAKEOBJDIRPREFIX settings? My change in r358909 will definitely not be effective if you already had a failed build between r358907 and r358909. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Build failed compiling ittnotify_static.pico
On 14 Mar 2020, at 17:24, Roman Bogorodskiy wrote:
>
> 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:
> '/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c'
> cc: error: no input files
> *** [ittnotify_static.pico] Error code 1
> Anyone else seeing this? Any suggestions for a fix?
> Thanks,
> Bob
I've been getting the same thing since yesterday. I think the file is
actually
ittnotify_static.cpp
>>>
>>>
>>> This is supposed to handle the rename, for some reason it's not happening
>>> on my machine.
>>>
>>> Makefile.inc1
>>>
>>> # 20200310 r358851 rename of openmp's ittnotify_static.c to .cpp
>>> .for f in ittnotify_static
>>> @if [ -e "${OBJTOP}/lib/libomp/.depend.${f}.pico" ] && \
>>> egrep -qw '${f}\.c' ${OBJTOP}/lib/libomp/.depend.${f}.pico; then \
>>> echo "Removing stale dependencies for ${f}"; \
>>> rm -f ${OBJTOP}/lib/libomp/.depend.${f}.* \
>>> ${OBJTOP}/obj-lib32/lib/libomp/.depend.${f}.* \
>>>
>>> ${LIBCOMPAT:D${LIBCOMPAT_OBJTOP}/lib/libomp/.depend.${f}.*}; \
>>> fi
>>> .endfor
>>
>> Hm, so during your buildworld, does it show "Removing stale dependencies
>> for ittnotify_static" or not? And is the .depend file there? Can you
>> check /usr/obj for the file .depend.ittnotify_static.pico, and list its
>> permissions?
>>
>> -Dimitry
>>
>
> I have the same issue updating one of my poudriere jails.
> I don't see "Removing stale dependencies ..." messages.
>
> I see a couple of ittnotify_static related messages:
>
> make[5]:
> /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/obj-lib32/lib/libomp/.depend.ittnotify_static.pico,
> 43: ignoring stale .depend for
> /workspace/poudriere/jails/current/usr/src/contrib/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c
> ...
> make[5]:
> /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/obj-lib32/lib/libomp/.depend.ittnotify_static.pico,
> 43: ignoring stale .depend for
> /workspace/poudriere/jails/current/usr/src/contrib/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.h
These are for the 32-bit stage. The initial fix I committed in r358907
worked for the main buildword stage, but apparently not for the 32-bit
stage, which stores its object files in a slightly different directory
(e.g. the obj-lib32 subpath).
Ed Maste tried to fix that up in r358909, but maybe it does not work in
all situations, for example with custom MAKEOBJDIRPREFIX settings?
> $ ls -al
> /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico
> -rw-r--r-- 1 root wheel 6565 Mar 14 19:30
> /usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico
What is in the first two lines of that file?
-Dimitry
signature.asc
Description: Message signed with OpenPGP
Re: Build failed compiling ittnotify_static.pico
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:
> >>> '/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c'
> >>> cc: error: no input files
> >>> *** [ittnotify_static.pico] Error code 1
> >>> Anyone else seeing this? Any suggestions for a fix?
> >>> Thanks,
> >>> Bob
> >> I've been getting the same thing since yesterday. I think the file is
> >> actually
> >> ittnotify_static.cpp
> >
> >
> > This is supposed to handle the rename, for some reason it's not happening
> > on my machine.
> >
> > Makefile.inc1
> >
> > # 20200310 r358851 rename of openmp's ittnotify_static.c to .cpp
> > .for f in ittnotify_static
> >@if [ -e "${OBJTOP}/lib/libomp/.depend.${f}.pico" ] && \
> >egrep -qw '${f}\.c' ${OBJTOP}/lib/libomp/.depend.${f}.pico; then
> > \
> >echo "Removing stale dependencies for ${f}"; \
> >rm -f ${OBJTOP}/lib/libomp/.depend.${f}.* \
> > ${OBJTOP}/obj-lib32/lib/libomp/.depend.${f}.* \
> >
> > ${LIBCOMPAT:D${LIBCOMPAT_OBJTOP}/lib/libomp/.depend.${f}.*}; \
> >fi
> > .endfor
>
> Hm, so during your buildworld, does it show "Removing stale dependencies
> for ittnotify_static" or not? And is the .depend file there? Can you
> check /usr/obj for the file .depend.ittnotify_static.pico, and list its
> permissions?
>
> -Dimitry
>
I have the same issue updating one of my poudriere jails.
I don't see "Removing stale dependencies ..." messages.
I see a couple of ittnotify_static related messages:
make[5]:
/usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/obj-lib32/lib/libomp/.depend.ittnotify_static.pico,
43: ignoring stale .depend for
/workspace/poudriere/jails/current/usr/src/contrib/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c
...
make[5]:
/usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/obj-lib32/lib/libomp/.depend.ittnotify_static.pico,
43: ignoring stale .depend for
/workspace/poudriere/jails/current/usr/src/contrib/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.h
$ ls -al
/usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico
-rw-r--r-- 1 root wheel 6565 Mar 14 19:30
/usr/obj/workspace/poudriere/jails/current/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico
$
Roman Bogorodskiy
signature.asc
Description: PGP signature
Re: Build failed compiling ittnotify_static.pico
On 14 Mar 2020, at 04:53, Masachika ISHIZUKA wrote: > >>> 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 delete obj for years, but I've not done that for a >> couple of years without any problems I've noticed. > > Thank you for information. > I'll try it. Obviously, cleaning up your /usr/obj will always help, but that is not the point of the fix. It should always be possible to do an incremental buildworld, but there is a deficiency in our dependency tracking system. When a file changes extension, but its basename stays the same, the tracking does not notice it. Assuming amd64 and the default /usr/src and /usr/obj setup, all the fix has to do is to remove the file /usr/obj/usr/src/amd64.amd64/lib/libomp/.depend.ittnotify_static.pico, since that will have a "stale" dependency on the old ittnotify_static.c file in it. It would still have been interesting to see why it did not work correctly for the original posters. -Dimitry signature.asc Description: Message signed with OpenPGP
Re: Build failed compiling ittnotify_static.pico
>>> 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 delete obj for years, but I've not done that for a >> couple of years without any problems I've noticed. > > Thank you for information. > I'll try it. After 'make cleanworld', it was able to make buildworld successfulley. Thanks. -- Masachika ISHIZUKA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
