public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "scaccopardo at tiscali dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14027] New: gcc (c++ not found)
Date: Thu, 05 Feb 2004 11:20:00 -0000	[thread overview]
Message-ID: <20040205112020.14027.scaccopardo@tiscali.it> (raw)

Hi,

I followed instructions and I created two dirs:
/usr/build and /usr/objdir

>From /usr/build I ./configured:

$ /usr/src/gcc-3.3.1-3/configure --enable-libjava --enable-languages=c,c++,java
--prefix=/usr/objdir

but I got the error:

[...]
configure: error:
The following requested languages were not found: c++
The following languages were available: c java treelang
Configure in /usr/build/gcc failed, exiting.

This is what is installed in my system:

$ $ cygcheck -c | grep gcc
gcc                  3.3.1-3            OK
gcc-g++              3.3.1-3            OK
gcc-java             3.3.1-3            OK
gcc-mingw-core       20031020-1         OK
gcc-mingw-g++        20031020-1         OK
gcc-mingw-java       20031020-1         OK

so g++ is installed, but it seems gcc is trying to use c++
as it was not external, but inside the compiler itself,
in fact I see the message:

The following languages were available: c java treelang

It's a very strange...

these are search dirs for gcc

$ gcc --print-search-dirs
install: /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/
programs: =/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/:/usr/lib/gcc-lib/i686-pc-cygwi
n/3.3.1/:/usr/lib/gcc-lib/i686-pc-cygwin/:/usr/lib/gcc/i686-pc-cygwin/3.3.1/:/us
r/lib/gcc/i686-pc-cygwin/:/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686
-pc-cygwin/bin/i686-pc-cygwin/3.3.1/:/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../..
/../../i686-pc-cygwin/bin/
libraries: =/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/:/usr/lib/gcc/i686-pc-cygwin/3
.3.1/:/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/lib/i686-
pc-cygwin/3.3.1/:/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwi
n/lib/:/usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../i686-pc-cygwin/3.3.1/:/usr
/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../:/lib/i686-pc-cygwin/3.3.1/:/lib/:/us
r/lib/i686-pc-cygwin/3.3.1/:/usr/lib/

This my PATH:

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/WINNT/system32:/cygdrive
/c/WINNT:/cygdrive/c/WINNT/System32/Wbem:/cygdrive/c/Programmi/j2sdk1.4.2_03/bin
:/cygdrive/c/PROGRA~1/NcFTP:/cygdrive/c/Programmi/Nokia/Tools/Nokia_Developers_S
uite_for_J2ME/bin:/cygdrive/c/Nokia/Update_Manager/bin:/cygdrive/c/Programmi/mys
ql/bin:/cygdrive/c/Programmi/BC5/BIN:.:/cygdrive/c/Programmi/Nokia/Tools/Nokia_D
evelopers_Suite_for_J2ME/bin:/cygdrive/c/Nokia/Update_Manager/bin

Later,

Davide

-- 
           Summary: gcc (c++ not found)
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: scaccopardo at tiscali dot it
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-02-05 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 11:20 scaccopardo at tiscali dot it [this message]
2004-02-05 16:45 ` [Bug c++/14027] " pinskia at gcc dot gnu 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=20040205112020.14027.scaccopardo@tiscali.it \
    --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).