You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Scott Cantor (Jira)" <ji...@apache.org> on 2021/10/14 18:34:00 UTC
[jira] [Updated] (SANTUARIO-528) (linux build) configure should
check for make
[ https://issues.apache.org/jira/browse/SANTUARIO-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Cantor updated SANTUARIO-528:
-----------------------------------
Fix Version/s: C++ 2.0.3
> (linux build) configure should check for make
> ---------------------------------------------
>
> Key: SANTUARIO-528
> URL: https://issues.apache.org/jira/browse/SANTUARIO-528
> Project: Santuario
> Issue Type: Bug
> Components: C++
> Affects Versions: C++ 2.0.2
> Reporter: Rod Widdowson
> Assignee: Scott Cantor
> Priority: Trivial
> Fix For: C++ 2.0.3
>
>
> I know that everybody always has it, but it turns out I didn't. Instead of saying I didn't have it (like it did for Gcc) it said:
> {code:java}
> config.status: executing depfiles commands
> config.status: error: in `/home/rdw/git/sp/xml-security-c-2.0.2':
> config.status: error: Something went wrong bootstrapping makefile fragments
> for automatic dependency tracking. Try re-running configure with the
> '--disable-dependency-tracking' option to at least be able to build
> the package (albeit without support for automatic dependency tracking).
> See `config.log' for more details{code}
> And sure enough the log file had the smoking gun
--
This message was sent by Atlassian Jira
(v8.3.4#803005)