[Asterisk-code-review] test: Check for the presence of open_memstream() to configure (asterisk[master])
Philip Prindeville
asteriskteam at digium.com
Tue May 3 15:16:49 CDT 2022
Attention is currently required from: Sean Bright.
Philip Prindeville has posted comments on this change. ( https://gerrit.asterisk.org/c/asterisk/+/18524 )
Change subject: test: Check for the presence of open_memstream() to configure
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> I _think_ I understand. […]
Yup, exactly. Asterisk is fairly portable, and I want to keep it that way... so bracketing any corner cases that might not build/run in all places ensures that the rest of it continues to do so...
--
To view, visit https://gerrit.asterisk.org/c/asterisk/+/18524
To unsubscribe, or for help writing mail filters, visit https://gerrit.asterisk.org/settings
Gerrit-Project: asterisk
Gerrit-Branch: master
Gerrit-Change-Id: Ifeaaf292dec21aa8076eab7acf8f42d05bedfaf7
Gerrit-Change-Number: 18524
Gerrit-PatchSet: 2
Gerrit-Owner: Philip Prindeville <philipp at redfish-solutions.com>
Gerrit-Reviewer: Friendly Automation
Gerrit-Reviewer: Sean Bright <sean at seanbright.com>
Gerrit-Attention: Sean Bright <sean at seanbright.com>
Gerrit-Comment-Date: Tue, 03 May 2022 20:16:49 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Sean Bright <sean at seanbright.com>
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-code-review/attachments/20220503/27e2b40a/attachment.html>
More information about the asterisk-code-review
mailing list