public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mtodorov@alu.hr To: gcc-gnats@gcc.gnu.org Subject: libgcj/2746: Bundled zip overvrites higher versioned zip in /usr/local/bin/zip Date: Sat, 05 May 2001 06:26:00 -0000 [thread overview] Message-ID: <20010505132005.28745.qmail@sourceware.cygnus.com> (raw) >Number: 2746 >Category: libgcj >Synopsis: Bundled zip overvrites higher versioned zip in /usr/local/bin/zip >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: mistaken >Submitter-Id: net >Arrival-Date: Sat May 05 06:26:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: mtodorov@alu.hr >Release: 2.95.1 >Organization: >Environment: alpha-dec-osf4.0b GCC 2.95.3 GNU make /usr/local/bin/zip higher version than bundled zip >Description: libgcj comes with bundled zip and builds it using this zip regardless of zip already existing on system in /usr/local/bin/zip that is a higher version. Unfortunatelly, it also overwrote zip 2.3 which was in /usr/local/bin/zip with bundled zip 2.1 which was built with libgcj -- and this without asking. This I would consider a non-elegant solution for the problem, or a bug. >How-To-Repeat: gzip -cd libgcj-2.95.1 | tar xvf - mkdir libgcj cd libgcj ../libgcj-2.95.1/configure gmake gmake install >Fix: Try to check whether there are zip and zlib on the system in ./configure script. If there are no zip and/or zlib, or they are older version than bundled packages, build bundled and install them. If bundled packages are older versions, do not install them, and choose whether to build with bundled or with what's present on system. If choice was made to use present on system packages, test them in configure script for correct working, the same as it is done with gcc complier in ./configure script. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-05-05 6:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-05 6:26 mtodorov [this message] 2001-06-07 15:55 tromey
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=20010505132005.28745.qmail@sourceware.cygnus.com \ --to=mtodorov@alu.hr \ --cc=gcc-gnats@gcc.gnu.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: linkBe 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).