public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/57028] [4.9 regression] Fortran bootstrap fails due to missing zlib.h
Date: Wed, 24 Apr 2013 16:54:00 -0000	[thread overview]
Message-ID: <bug-57028-4-fkclrQROuy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57028-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #3 from Mikael Pettersson <mikpe at it dot uu.se> 2013-04-24 16:54:41 UTC ---
As far as I understand it, there are two issues:

1. zlib isn't built unless some explicitly enabled component demands it; in my
case (on x86_64) zlib was built since I had java enabled, but nothing in
Fortran appears to declare a dependency on zlib.  Maybe
gcc/fortran/config-lang.in is the place to declare that?

2. The in-tree zlib isn't added automatically to include and library paths,
components need to check for with_system_zlib and adjust their paths
accordingly, c.f. libjava/configure.ac.


  parent reply	other threads:[~2013-04-24 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22  8:27 [Bug bootstrap/57028] New: " mikpe at it dot uu.se
2013-04-22 12:28 ` [Bug bootstrap/57028] " rguenth at gcc dot gnu.org
2013-04-24 15:09 ` gretay at gcc dot gnu.org
2013-04-24 15:28 ` jb at gcc dot gnu.org
2013-04-24 16:54 ` mikpe at it dot uu.se [this message]
2013-04-24 20:03 ` jb at gcc dot gnu.org
2013-04-25  9:16 ` mikpe at it dot uu.se
2013-04-25 13:50 ` mikpe at it dot uu.se
2013-04-25 19:19 ` jb at gcc dot gnu.org
2013-04-25 19:20 ` jb at gcc dot gnu.org
2013-04-25 19:20 ` jb at gcc dot gnu.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-57028-4-fkclrQROuy@http.gcc.gnu.org/bugzilla/ \
    --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).