public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/7125] libz is built even if configured with --with-system-zlib
Date: Sat, 24 Jan 2004 06:25:00 -0000	[thread overview]
Message-ID: <20040124062500.30346.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020625135600.7125.mark@moxienet.com>


------- Additional Comments From aj at gcc dot gnu dot org  2004-01-24 06:24 -------
It's still built - both for target and each host multiarch (here on Linux/x86-64):
$ ls zlib/
Makefile      config.log     gzio.o      inflate.o   libz.a
adler32.o     config.status  infblock.o  inftrees.o  trees.o
compress.o    crc32.o        infcodes.o  infutil.o   uncompr.o
config.cache  deflate.o      inffast.o   libtool     zutil.o

$ ls x86_64-suse-linux-gnu/zlib/ x86_64-suse-linux-gnu/32/zlib/
x86_64-suse-linux-gnu/32/zlib/:
Makefile      config.status  infblock.lo  inflate.o               trees.lo
adler32.lo    crc32.lo       infblock.o   inftrees.lo             trees.o
adler32.o     crc32.o        infcodes.lo  inftrees.o              uncompr.lo
compress.lo   deflate.lo     infcodes.o   infutil.lo              uncompr.o
compress.o    deflate.o      inffast.lo   infutil.o               zutil.lo
config.cache  gzio.lo        inffast.o    libtool                 zutil.o
config.log    gzio.o         inflate.lo   libzgcj_convenience.la

x86_64-suse-linux-gnu/zlib/:
Makefile      config.status  infblock.lo  inflate.o               multilib.out
adler32.lo    crc32.lo       infblock.o   inftrees.lo             trees.lo
adler32.o     crc32.o        infcodes.lo  inftrees.o              trees.o
compress.lo   deflate.lo     infcodes.o   infutil.lo              uncompr.lo
compress.o    deflate.o      inffast.lo   infutil.o               uncompr.o
config.cache  gzio.lo        inffast.o    libtool                 zutil.lo
config.log    gzio.o         inflate.lo   libzgcj_convenience.la  zutil.o

I'm not sure whether it is used or not.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
   Last reconfirmed|2003-11-19 19:21:28         |2004-01-24 06:24:57
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7125


  parent reply	other threads:[~2004-01-24  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020625135600.7125.mark@moxienet.com>
2003-06-02  3:45 ` dhazeghi@yahoo.com
2004-01-23 21:00 ` dhazeghi at yahoo dot com
2004-01-24  6:25 ` aj at gcc dot gnu dot org [this message]
2005-06-16 14:51 ` [Bug other/7125] " pinskia at gcc dot gnu dot org
     [not found] <bug-7125-4@http.gcc.gnu.org/bugzilla/>
2012-02-06 15:10 ` [Bug bootstrap/7125] " richard.purdie at linuxfoundation dot org
2012-02-06 16:25 ` richard.purdie at linuxfoundation dot org
2015-04-01  3:34 ` hjl.tools at gmail dot com

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=20040124062500.30346.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).