Use of path segments not supported in this build of libEST. #99
Comments
|
Hello,
In order for libEST to support the use of path segments it needs to
be built with access to another library that provides for the
parsing and manipulation of URIs. This library is called
uriparser. https://github.com/uriparser/uriparser
The last version that was tested with LibEST is 0.9.1, but I suspect
the latest code in its master branch will work.
Once you have uriparser installed on your development system you
point the build of LibEST to it with the configure option of
--with-uriparser-dir=.
If you're going to be using LibEST I would suggest building and
referring to the documentation that comes with it. The building of
the documentation PDF is defined in README.doxy. The output from
doxygen may not be the cleanest, but it should result in a
refman.pdf file. How to build uriparser as well as how to point
libEST to it in the LibEST build is explained in this documentation
as well as a number of other optional capabilities.
Hope this helps,
Pete
On 3/1/21 3:29 PM, dieselnutjob wrote:
Hi
I am trying to use estclient in an environment where I have no
control of the server (it's provided by another company).
The other company has given me this URI
https://aserver/.well-known/est/astring/simpleenroll
from this I deduce that I need to use this command
./estclient -e -s aserver --path-seg astring -p 443 -h apassword
-o /tmp
however I get this error:-
EST [ERROR][est_client_set_server:4644]--> Use of path
segments not supported in this build of libEST.
Have I understood this correctly and is there anything that I
can do about this?
—
You are receiving this because you are subscribed to this
thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "#99",
"url": "#99",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
|
Just to let you know that I am working on this. entering extended mode ! LaTeX Error: File `xtab.sty' not found. Type X to quit or to proceed, Enter file name: |
|
I completely understand how you feel. I built the latest reference manual for LibEST 3.2.0p and uploaded here. Pete |
|
Thanks. As it goes after posting I managed to compile the manual quite easily on my personal Manjaro system and I'm pretty sure it would have been even easier on a Debian based system. This is purely because if you are missing a command and want to know what package to install to get it it's so much easier with these systems. Anyway. As a result of all this I started looking for uriparser and uriparser-devel on the Oracle 8 box. I came across this link which seems to suggest that uriparser is deprecated in EL8 and I can't help thinking that this will be a "problem" if libest is ever going to be properly accepted and supported by any EL vendor. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/7.9_release_notes/index Would it be possible to add some uriparser code into libest itself so that use of another library isn't necessary? It someone was ever going to make an rpm installer of libest wouldn't that make it easier to package maintain and more likely to be officially taken up? I'm not a C developer so apologies if that's silly in some way. |
|
I can't currently compile uriparser from source either. Now I get [ 97%] Linking CXX executable testrunner |
|
--disable-test ??
From configure.ac
## Option --disable-test
AC_ARG_ENABLE(test, [
==============================================================================
Extra options:
AS_HELP_STRING(
[--disable-test], [disable 'make check' and libgtest dependency]
)], [
URI_TEST_YESNO=${enableval}
],[
URI_TEST_YESNO=yes
])
Pete
…On 3/6/21 8:40 AM, dieselnutjob wrote:
I can't currently compile uriparser from source either.
My first attempt resulted in complaints about no gtest
The only gtest and gtest-devel packages I could find were from Fedora
EPEL for EL7, none for EL8, so I went with those.
Now I get
[ 97%] Linking CXX executable testrunner
CMakeFiles/testrunner.dir/test/MemoryManagerSuite.cpp.o: In function
|testing::Message::GetString() const':
MemoryManagerSuite.cpp:(.text._ZNK7testing7Message9GetStringEv[_ZNK7testing7Message9GetStringEv]+0x2a):
undefined reference to
|testing::internal::StringStreamToString(std::__cxx11::basic_stringstream<char,
std::char_traits, std::allocator >*)'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/testrunner.dir/build.make:356: testrunner]
Error 1
make[1]: *** [CMakeFiles/Makefile2:142: CMakeFiles/testrunner.dir/all]
Error 2
make: *** [Makefile:141: all] Error 2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#99 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABU7INV7BGSQLFBSY2OBAALTCIWDZANCNFSM4YNIMLVQ>.
|
Hi
I am trying to use estclient in an environment where I have no control of the server (it's provided by another company).
The other company has given me this URI
https://aserver/.well-known/est/astring/simpleenroll
from this I deduce that I need to use this command
./estclient -e -s aserver --path-seg astring -p 443 -h apassword -o /tmp
however I get this error:-
EST [ERROR][est_client_set_server:4644]--> Use of path segments not supported in this build of libEST.
Have I understood this correctly and is there anything that I can do about this?
The text was updated successfully, but these errors were encountered: