From: Eli Schwartz <eschwartz93@gmail.com>
To: ~eschwartz <eschwartz@archlinux.org>, bzip2-devel@sourceware.org
Subject: Re: [PATCH bzip2 2/6] port the build configuration to autoconf
Date: Thu, 9 Jun 2022 01:56:14 -0400 [thread overview]
Message-ID: <665e2fe0-9660-f744-a266-9c0313777b73@gmail.com> (raw)
In-Reply-To: <165475384722.17277.18269615533597437835-1@git.sr.ht>
On 6/3/22 12:20 AM, ~eschwartz wrote:
> From: Eli Schwartz <eschwartz93@gmail.com>
>
> This doesn't investigate the topic of fully autotools'ing the build,
> with automake and libtool, as there are libtool compatibility
> considerations to take into account.
>
> All we do for now is make the standard ./configure script that formats
> the Makefile in order to respect some low-level standards:
>
> - GNU directory variables to control output locations.
> - respect $DESTDIR if given.
> - check for $CC, $CFLAGS, etc
> - including cross-compile support
> ---
I was unable to actually test `make dist`, by the way, as it didn't seem
to want to play nicely with texlive on my system.
$ make manual.pdf
./xmlproc.sh -pdf manual.xml
Creating manual.pdf ...
Making portrait pages on USletter paper (8.5inx11in)
Cleaning up: output manual.fmt *.aux manual.fo manual.log texput.log *.out
deleting output
deleting manual.fmt
deleting *.aux
rm: cannot remove '*.aux': No such file or directory
deleting manual.fo
deleting manual.log
deleting texput.log
deleting *.out
rm: cannot remove '*.out': No such file or directory
make: *** [Makefile:234: manual.pdf] Error 1
This shell script for creating the manual fails to create either the pdf
file, or the temporary files that it then fails to remove... but it
doesn't say why it failed so it's not clear whether I have a
misconfiguration or what.
--
Eli Schwartz
next prev parent reply other threads:[~2022-06-09 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 3:45 [PATCH bzip2 1/6] install relative symlinks ~eschwartz
2022-06-03 4:20 ` [PATCH bzip2 2/6] port the build configuration to autoconf ~eschwartz
2022-06-09 5:56 ` Eli Schwartz [this message]
2022-06-03 4:48 ` [PATCH bzip2 4/6] make a couple program aliases symlinks instead of copies ~eschwartz
2022-06-03 4:54 ` [PATCH bzip2 5/6] install man page symlinks for a couple more symlinked commands ~eschwartz
2022-06-03 5:09 ` [PATCH bzip2 6/6] install a pkg-config file with instructions for linking to libbz2 ~eschwartz
2022-06-09 5:52 ` Eli Schwartz
2022-10-23 16:03 ` Sam James
2022-06-09 4:50 ` [PATCH bzip2 3/6] shared Makefile: add install rule ~eschwartz
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=665e2fe0-9660-f744-a266-9c0313777b73@gmail.com \
--to=eschwartz93@gmail.com \
--cc=bzip2-devel@sourceware.org \
--cc=eschwartz@archlinux.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 read-only IMAP folder(s) and NNTP newsgroup(s).