-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add xmlsec/1.2.30 #3314
add xmlsec/1.2.30 #3314
Conversation
Sorry, the build is only launched for Early Access Program users. You can request access writing in this issue. |
Sorry, the build is only launched for Early Access Program users. You can request access writing in this issue. |
Some configurations of 'xmlsec/1.2.30' failed in build 3 (
|
Some configurations of 'xmlsec/1.2.30' failed in build 4 (
|
Co-authored-by: Anonymous Maarten <[email protected]>
Co-authored-by: Anonymous Maarten <[email protected]>
Some configurations of 'xmlsec/1.2.30' failed in build 5 (
|
Co-authored-by: Anonymous Maarten <[email protected]>
An unexpected error happened and has been reported. Help is on its way! 🏇 |
Co-authored-by: Anonymous Maarten <[email protected]>
Co-authored-by: Anonymous Maarten <[email protected]>
Co-authored-by: Anonymous Maarten <[email protected]>
An unexpected error happened and has been reported. Help is on its way! 🏇 |
Co-authored-by: Anonymous Maarten <[email protected]>
Some configurations of 'xmlsec/1.2.30' failed in build 23 (
|
All green in build 24 (
|
@madebr I fixed the build, initializing the autotools.libs variable with the syslib pthread (for linux). Maybe not the cleanest solution, but I can't invest a lot of time this week. Could you please have a look at it? |
All green in build 25 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting --with-openssl=
to yes/no
fixed it for me on gcc9.
By using self.deps_info["openssl"].rootpath
, the pc files are bypassed.
Co-authored-by: Anonymous Maarten <[email protected]>
All green in build 26 (
|
Co-authored-by: SpaceIm <[email protected]>
@uilianries @danimtb Sometimes I don't know why the build fails. Build is red, conan-center-index-bot doesn't reply. What's the best way to retrigger the build? Changing the initial description seems to work only if you reference another issue. Should I close/reopen the pr or add an empty commit to retrigger the build? |
All green in build 28 (
|
Co-authored-by: SpaceIm <[email protected]>
All green in build 29 (
|
Specify library name and version: xmlsec/1.2.30
conan-center hook activated.
Fixes #1876