Re: How to compile hashlib.c for testing?

Path	csiph.com!goblin3!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From	Eduardo Bustamante <dualbus@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: How to compile hashlib.c for testing?
Date	Thu, 27 Dec 2018 17:34:49 -0800
Lines	10
Approved	bug-bash@gnu.org
Message-ID	<mailman.6429.1545961031.1284.bug-bash@gnu.org> (permalink)
References	<CABrM6wm+x0hGuSVYeRLSE9=6vuadxP++4+gSoG+Tm7_yYN4Duw@mail.gmail.com> <31ae9367-7968-aff5-d0e8-0f9da667d584@case.edu> <CABrM6w=a7NyF8xBkooeJojkAK_b=_rz9VsnWt2MWV3HN4BA9Eg@mail.gmail.com>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	text/plain; charset="UTF-8"
X-Trace	usenet.stanford.edu 1545961032 12694 208.118.235.17 (28 Dec 2018 01:37:12 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	Chet Ramey <chet.ramey@case.edu>, bug-bash <bug-bash@gnu.org>
To	Peng Yu <pengyu.ut@gmail.com>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bGUye8fxgnKS32pL+xRDTqhy8ka4okMrIOEfWcIgj7Y=; b=KzspHIlwaD7+dxgE4jQ6KB8qc2fZdPizQMpPvx4Z29PSmwcNa+Vka3r3mqxIIqpbsu UA03SkMRzdHfbt7sxf03/FKGj7fJGbrDtOlRYAIKa04q6LNjTUhpTtGW7DdCV5Pnlw8I avxzZZID5IDiVn3t8q244vlbSMAiJW5T40GyDcFOpQZuKMcBdoozfWvl+/uPwUjbgNMP HeRSQdjJ/1rqzwCmt4Z+7QJQQ5/uJZ8+f6QlWo8zm15o9ijw7elJvNLd91ov8Or3d4hx t7Xs84YEdz+cDlzuw+puwMw3D1FSqVGEz7c20OfkMaLG40CCDpM3QgMAO5S8lomfarmM a73A==
X-Google-DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bGUye8fxgnKS32pL+xRDTqhy8ka4okMrIOEfWcIgj7Y=; b=FQh6D9JVYYwZYIOf6s+SeDMeqYvOoWkAgkNkup9hKm6pdytoPjYgHV6eA/h1iKvnQM EIGzglKLO136tMvHW7Ns/isSN7n8LebGQ6F7mECSryNtYa90oYrobEqxzUwDKZp2BNSp +LlsHqatqZ7lxsJwgSQCsFsOqjTBflO44loHM3vwd1ASKvTklzye/T/b0rlxg/lVzBI2 Czn9+hUANeQA05/ZUldUBRVudhiT4FHt7Ayij6z4ygbA4CStQWY9HxYRZvPiDeBGeEsA yHkza/0vIW0fUjn524OKb5jETFdXDbBxVX8ww81qZkeiYaSq5vN8je5OQcU2hKYJUEUB VU2g==
X-Gm-Message-State	AJcUukekM0+GeIQRzOMhPU9e5PDmrZ2RSJoaCUpnUYn8r4/Ab3L8Yrim qc7oPV16+38P9jbj7+FuRyLNpg49oqPQJNXP5Dg=
X-Google-Smtp-Source	ALg8bN6wwGOpPeh8GFeMqPmFtcA2RTVcN82ZKsdP9oSaJ5ygMhCbYovst7/qRDuM6MCf4F4NJ3XVs9OgSVl9ykvFCJw=
X-Received	by 2002:a2e:8719:: with SMTP id m25-v6mr16173215lji.121.1545960904480; Thu, 27 Dec 2018 17:35:04 -0800 (PST)
In-Reply-To	<CABrM6w=a7NyF8xBkooeJojkAK_b=_rz9VsnWt2MWV3HN4BA9Eg@mail.gmail.com>
X-detected-operating-system	by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From	2a00:1450:4864:20::22d
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.21
Precedence	list
List-Id	Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe	<https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive	<http://lists.gnu.org/archive/html/bug-bash/>
List-Post	<mailto:bug-bash@gnu.org>
List-Help	<mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe	<https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref	csiph.com gnu.bash.bug:14978

Show key headers only | View raw

On Thu, Dec 27, 2018 at 5:15 PM Peng Yu <pengyu.ut@gmail.com> wrote:
(...)
> Since the main() function is already there, why there is not already
> an easy way to compile it? How do you do unit-testing then for the
> code?

This is very easy to figure out from the source code, right :)?

(Hint: there is no "unit" testing in bash)

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: How to compile hashlib.c for testing? Eduardo Bustamante <dualbus@gmail.com> - 2018-12-27 17:34 -0800

csiph-web