<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<p style="color: #777777;">

<a href="https://gitlab.com/nmav">Nikos Mavrogiannopoulos</a>

commented:

</p>

<div style="">

<p dir="auto">The problem I see is that this is very easy to break as we do not test for compilation under these conditions. If I remember well the minimal build does not build the tools because it was too complex to manage these scenarios for the tools. What's your goal in this MR, to compile the tools without GOST or to revive the minimal build, or even to introduce a new minimal build which is kind of supported? My point is that in all of these cases we would need to introduce a test build which actually tests that scenario.</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/merge_requests/1143#note_265659882">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/sent_notifications/5bea97ca64a7bf2eb3c82301c1f6142d/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/1143#note_265659882"}}</script>

</p>

</div>

</body>

</html>