From: merlyn@stonehenge•com (Randal L. Schwartz)
To: git@vger•kernel.org
Subject: use of warn (usage.c) conflicts with BSD
Date: Mon, 26 Mar 2007 06:03:50 -0700 [thread overview]
Message-ID: <86bqig40nd.fsf@blue.stonehenge.com> (raw)
I finally tracked down all the (albeit inconsequential) errors I was getting
on both OpenBSD and OSX. It's the warn() function in usage.c. There's
warn(3) in BSD-style distros. It'd take a "great rename" to change it, but if
someone with better C skills than I have could do that, my linker and I would
appreciate it.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge•com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
reply other threads:[~2007-03-26 13:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bqig40nd.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox