public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppohja at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12596] New: configure setting --with-libiconv-prefix doesn't get passed to gcc-subdir
Date: Mon, 13 Oct 2003 13:14:00 -0000	[thread overview]
Message-ID: <20031013131412.12596.ppohja@iki.fi> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: configure setting --with-libiconv-prefix doesn't get
                    passed to gcc-subdir
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ppohja at iki dot fi
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i386-unknown-freebsd4.8
  GCC host triplet: i386-unknown-freebsd4.8
GCC target triplet: i386-unknown-freebsd4.8

Telling the configure to use some dir for finding libiconv libraries and 
headers doesn't get passed to the gcc-subdir. This causes the HAVE_ICONV flag 
to be set there, but the compilation doesn't find the needed headers (see the 
attached error message).

Manually adding the wanted directory (/usr/local/include) to the INCLUDES in 
gcc/Makefile allows the compilation to be continued.

The compilation fails as follows:
--- clip ---
gcc   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prototypes -pedantic -Wno-long-long -fno-common   -DHAVE_CONFIG_H    -I. -I. -
I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../intl \
  -DGCC_INCLUDE_DIR=\"/home/ppohja/gcc/lib/gcc/i386-unknown-
freebsd4.8/3.4/include\" -
DGPLUSPLUS_INCLUDE_DIR=\"/home/ppohja/gcc/lib/gcc/i386-unknown-
freebsd4.8/3.4/../../../..`echo /home/ppohja/gcc | sed -
e 's|^/home/ppohja/gcc||' -e 's|/[^/]*|/..|g'`/include/c++/3.4\" -
DGPLUSPLUS_TOOL_INCLUDE_DIR=\"/home/ppohja/gcc/lib/gcc/i386-unknown-
freebsd4.8/3.4/../../../..`echo /home/ppohja/gcc | sed -
e 's|^/home/ppohja/gcc||' -e 's|/[^/]*|/..|g'`/include/c++/3.4/i386-unknown-
freebsd4.8\" -DGPLUSPLUS_BACKWARD_INCLUDE_DIR=\"/home/ppohja/gcc/lib/gcc/i386-
unknown-freebsd4.8/3.4/../../../..`echo /home/ppohja/gcc | sed -
e 's|^/home/ppohja/gcc||' -e 's|/[^/]*|/..|g'`/include/c++/3.4/backward\" -
DLOCAL_INCLUDE_DIR=\"/usr/local/include\" -
DCROSS_INCLUDE_DIR=\"/home/ppohja/gcc/lib/gcc/i386-unknown-
freebsd4.8/3.4/../../../../i386-unknown-freebsd4.8/sys-include\" -
DTOOL_INCLUDE_DIR=\"/home/ppohja/gcc/lib/gcc/i386-unknown-
freebsd4.8/3.4/../../../../i386-unknown-freebsd4.8/include\"  \
  -c ../../gcc/gcc/cppdefault.c -o cppdefault.o
gcc -c   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-
prototypes -pedantic -Wno-long-long -fno-common   -DHAVE_CONFIG_H    -I. -I. -
I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -
I../intl ../../gcc/gcc/c-ppoutput.c -o c-ppoutput.o
In file included from ../../gcc/gcc/c-ppoutput.c:25:
../../gcc/gcc/cpphash.h:29: iconv.h: No such file or directory
gmake[2]: *** [c-ppoutput.o] Error 1
gmake[2]: Leaving directory `/usr/home/ppohja/compile/objdir/gcc'
gmake[1]: *** [stage1_build] Error 2
gmake[1]: Leaving directory `/usr/home/ppohja/compile/objdir/gcc'
gmake: *** [bootstrap] Error 2
gmake bootstrap  0.44s user 0.48s system 107% cpu 0.847 total


             reply	other threads:[~2003-10-13 13:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 13:14 ppohja at iki dot fi [this message]
2003-11-08 21:12 ` [Bug bootstrap/12596] " dhazeghi at yahoo dot com
2004-01-17 23:20 ` dhazeghi at yahoo dot com
2004-02-27 15:54 ` pinskia at gcc dot gnu dot org
2004-03-04 16:17 ` pinskia at gcc dot gnu dot org
2004-03-04 16:41 ` artem at bizlink dot ru
2004-03-04 17:52 ` artem at bizlink dot ru
2004-03-12  8:28 ` artem at bizlink dot ru

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=20031013131412.12596.ppohja@iki.fi \
    --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).