public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jgutierrez@e-net.com.mx
To: gcc-gnats@gcc.gnu.org
Subject: c++/4369: Can't create executables (dont work)
Date: Thu, 20 Sep 2001 10:46:00 -0000	[thread overview]
Message-ID: <20010920174452.6733.qmail@sourceware.cygnus.com> (raw)

>Number:         4369
>Category:       c++
>Synopsis:       Can't create executables (dont work)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Sep 20 10:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Tyr to compile the qpopper file configure or anyone else
>Release:        3.0.1
>Organization:
>Environment:
solaris intel version 8
>Description:

When i try to compile a file (configure of qpopper or else) the system give me the next message.

# ./configure
loading cache ./config.cache
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.


>How-To-Repeat:
Get the package og GNUgcc from sunfreware web page. Then the qpopper4.0.3 from eudora web page. Then install the gcc. uncompress the qpopper file and try to run the command ./configure in the directory created by the archive qpopper4.0.3
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-09-20 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 10:46 jgutierrez [this message]
2001-09-20 11:16 Phil Edwards
2001-09-20 13:57 pme

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=20010920174452.6733.qmail@sourceware.cygnus.com \
    --to=jgutierrez@e-net.com.mx \
    --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: 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).