public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: "slyich at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/30001] New: Port to autoconf build system (maybe use sbrabec's patch?)
Date: Sat, 14 Jan 2023 11:47:23 +0000	[thread overview]
Message-ID: <bug-30001-11876@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30001

            Bug ID: 30001
           Summary: Port to autoconf build system (maybe use sbrabec's
                    patch?)
           Product: bzip2
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bzip2
          Assignee: nobody at sourceware dot org
          Reporter: slyich at gmail dot com
                CC: bzip2-devel at sourceware dot org
  Target Milestone: ---

To ease cross-compilation of bzip2 NixOS uses

   
https://ftp.suse.com/pub/people/sbrabec/bzip2/for_downstream/bzip2-1.0.6.2-autoconfiscated.patch
version of autoconf build system for bzip2.

WDYT of merging it upstream in some form?

Currently NixOS generates ./configure using autoconf and automake. NixOS would
prefer using autoconf-based upstream bzip2 release tarball without a dependency
on these development tools.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-01-14 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 11:47 slyich at gmail dot com [this message]
2023-01-14 16:49 ` [Bug bzip2/30001] " sam at gentoo dot org
2023-02-12 17:13 ` eschwartz at archlinux dot org
2023-02-12 19:22 ` noloader at gmail dot com
2024-04-20  7:44 ` sam at gentoo dot org

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=bug-30001-11876@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=bzip2-devel@sourceware.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).