public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Markus.Elfring at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56709] Should the passed command parameters result into the same error messages for a configuration test?
Date: Sun, 24 Mar 2013 14:48:00 -0000	[thread overview]
Message-ID: <bug-56709-4-QPvdvmC8CE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56709-4@http.gcc.gnu.org/bugzilla/>


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

Markus Elfring <Markus.Elfring at web dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #3 from Markus Elfring <Markus.Elfring at web dot de> 2013-03-24 14:48:24 UTC ---
(In reply to comment #1)
> What is the question?

1. Why do I get error messages about "undefined references" here?

2. Should the shown commands be equivalent?


> You've only shown one GCC command, what is the other one?

>From ~/Projekte/OpalVoip/OPAL/3.10.10/config.log:
configure:6101: g++ -o conftest  -Wall -Wextra -Wstrict-aliasing -Wfloat-equal
-Wno-comment -Wno-unused -Winit-self -Wno-missing-field-initializers -DP_64BIT
-DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fexceptions -I/usr/local/include
-I/usr/include/SDL   -felide-constructors -Wreorder -fPIC -DP_64BIT
-DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fexceptions -I/usr/local/include
-I/usr/include/SDL   -felide-constructors -Wreorder   -DP_64BIT -DPTRACING=1
-D_REENTRANT -D_GNU_SOURCE=1 -fexceptions -I/usr/local/include
-I/usr/include/SDL   conftest.cpp  -L/usr/local/lib64 -lpt_s -lrt -lsasl2
-lldap -llber -lldap_r -lssl -lcrypto -lexpat -llua -lSDL -lpthread -lodbc
-lresolv -ldl   >&5



(In reply to comment #2)

It seems that no other software developer was interested so far to add
constructive feedback for this issue on the mailing list.


  parent reply	other threads:[~2013-03-24 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 13:34 [Bug c++/56709] New: " Markus.Elfring at web dot de
2013-03-24 14:07 ` [Bug c++/56709] " redi at gcc dot gnu.org
2013-03-24 14:08 ` redi at gcc dot gnu.org
2013-03-24 14:48 ` Markus.Elfring at web dot de [this message]
2013-03-24 14:59 ` redi 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-56709-4-QPvdvmC8CE@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).