<!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=utf-8" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<div>

<blockquote dir="auto">

<blockquote>

<p>Is portability the goal of our test suite?</p>

</blockquote>

</blockquote>

<blockquote dir="auto">

<p>Clearly yes. Building GnuTLS on a platform is one thing. Another is the correct functionality on that platform. The typical, approved and widely used build+test sequence is <code>./configure && make && make check && sudo make install</code>. Would you really recommend to leave out <code>make check</code> ?</p>

</blockquote>

<p dir="auto">No that was not what I suggested. make check will run everywhere though it may require bash to be available. I may be missing something, but I do not see it as an unreasonable requirement given the list of dependencies that we already have.</p>

</div>

</div>

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

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

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/merge_requests/809#note_118843082">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/c304372db610c18c0aea694aebd49720/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/809#note_118843082"}}</script>

</p>

</div>

</body>

</html>