On 12/21/20 4:49 PM, Daniel Stenberg wrote:
> +        if (/^\#\s*\z/) {
> +            next;
> +        }

I applied that and test 1167 still fails :

alpha $
alpha $ diff -u  badsymbols.pl.orig badsymbols.pl
--- badsymbols.pl.orig  Sun Dec 20 12:25:10 2020
+++ badsymbols.pl       Mon Dec 21 23:30:04 2020
@@ -90,6 +90,9 @@
         if($skipit) {
             next;
         }
+        if (/^\#\s*\z/) {
+            next;
+        }
         if ( /enum\s+(\S+\s+)?{/ .. /}/ ) {
             s/^\s+//;
             chomp;
alpha $

alpha $ ./runtests.pl -p 1167
********* System characteristics ********
* curl 7.74.0 (sparc64-sun-solaris2.10)
* libcurl/7.74.0 OpenSSL/1.1.1i zlib/1.2.11 libidn2/2.3.0 libssh2/1.9.0
* Features: alt-svc AsynchDNS HTTPS-proxy IDN IPv6 Largefile libz NTLM
NTLM_WB SSL TLS-SRP UnixSockets
* Disabled:
* Host: alpha
* System: SunOS alpha 5.10 Generic_150400-65 sun4u sparc
SUNW,SPARC-Enterprise
* OS: solaris
* Servers: HTTP-IPv6 HTTP-unix FTP-IPv6
* Env:
* Seed: 211840
*****************************************
test 1167...[Verify curl prefix of public symbols in header files]

perl -I.  returned 1, when expecting 0
 exit FAILED
== Contents of files in the log/ dir after test 1167
=== Start of file commands.log
 perl -I. ./badsymbols.pl ./.. >log/stdout1167 2>log/stderr1167
=== End of file commands.log
=== Start of file ftpserver.cmd
 Testnum 1167
=== End of file ftpserver.cmd
=== Start of file stdout1167
 Bad symbols in public header files:
   #
   #
   #
   #
.
.  lots of these lines
.
   #
   #
   #
   #
   #
=== End of file stdout1167

 - abort tests
TESTDONE: 0 tests out of 1 reported OK: 0%

TESTFAIL: These test cases failed: 1167

TESTDONE: 1 tests were considered during 0 seconds.
alpha $

Also I attached the badsymbols_patched.log.xz here.

Dennis

Attachment: badsymbols_patched.log.xz
Description: application/xz

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html

Reply via email to