Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: calc: update to 2.12.7.6
Date: Fri, 12 Feb 2021 19:22:22 +0100	[thread overview]
Message-ID: <20210212182222.ASLkS0AWztK6CAcgj0wsgFfjR-VlS5PI5II4ZburwnA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28681@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/28681#issuecomment-778361879

Comment:
Cross builds are running a bunch of these, but for the host, to generate headers:

```
forming have_unistd.h
have_unistd.h formed
forming have_stdlib.h
have_stdlib.h formed
gcc -DCALC_SRC -DCUSTOM -Wall  -march=native   -fPIC longbits.c -c
rm -f longbits
gcc -DCALC_SRC -DCUSTOM -Wall  -march=native   -fPIC longbits.o -o longbits
forming longbits.h
longbits.h formed
forming align32.h
align32.h formed
forming have_string.h
have_string.h formed
forming args.h
args.h formed
forming calcerr.h
calcerr.h formed
forming conf.h
conf.h formed
gcc -DCALC_SRC -DCUSTOM -Wall  -march=native   -fPIC  endian.c -c
rm -f endian
gcc -DCALC_SRC -DIt's likely to beCUSTOM -Wall  -march=native   -fPIC endian.o -o endian
forming endian_calc.h
endian_calc.h formed
forming have_fpos.h
have_fpos.h formed
forming have_posscl.h
have_posscl.h formed
forming have_fpos_pos.h
have_fpos_pos.h formed
forming have_offscl.h
have_offscl.h formed
forming fposval.h
fposval.h formed
forming have_const.h
have_const.h formed
forming have_memmv.h
have_memmv.h formed
forming have_newstr.h
have_newstr.h formed
forming have_times.h
have_times.h formed
forming have_uid_t.h
have_uid_t.h formed
forming terminal.h
terminal.h formed
forming have_ustat.h
have_ustat.h formed
forming have_getsid.h
have_getsid.h formed
forming have_getpgid.h
have_getpgid.h formed
forming have_gettime.h
have_gettime.h formed
forming have_getprid.h
have_getprid.h formed
forming have_urandom.h
have_urandom.h formed
forming have_rusage.h
have_rusage.h formed
forming have_strdup.h
have_strdup.h formed
forming have_unused.h
have_unused.h formed
forming calcerr.c
calcerr.c formed
```

And most are likely to be quite wrong, I think.

  parent reply	other threads:[~2021-02-12 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12  1:12 [PR PATCH] " saqfish
2021-02-12  1:25 ` [PR PATCH] [Updated] " saqfish
2021-02-12  1:34 ` ericonr
2021-02-12 18:15 ` Chocimier
2021-02-12 18:22 ` ericonr [this message]
2021-02-12 22:47 ` [PR PATCH] [Updated] " saqfish
2021-02-12 22:50 ` saqfish
2021-02-12 22:55 ` [PR PATCH] [Closed]: " saqfish

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=20210212182222.ASLkS0AWztK6CAcgj0wsgFfjR-VlS5PI5II4ZburwnA@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).