public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "r dot ford at cox dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30868]  New: can't compile empty main in c on hppa 11iv1 (11.11)
Date: Tue, 20 Feb 2007 06:11:00 -0000	[thread overview]
Message-ID: <bug-30868-14126@http.gcc.gnu.org/bugzilla/> (raw)

# gcc -o main.out main.c
/usr/lib/dld.sl: Unresolved symbol: pthread_mutex_lock (code)  from
/usr/local/libexec/gcc/hppa2.0w-hp-hpux11.11/4.1.1/cc1
gcc: Internal error: Aborted (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
# cc -o main.out main.c
# ./main.out 
# cat main.c
int main(int argc,char** argv)
{

}
# gcc -o main.out main.c
/usr/lib/dld.sl: Unresolved symbol: pthread_mutex_lock (code)  from
/usr/local/libexec/gcc/hppa2.0w-hp-hpux11.11/4.1.1/cc1
gcc: Internal error: Aborted (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
# cc -o main.out main.c
# ./main.out 
# cat main.c
int main(int argc,char** argv)
{

}
#


-- 
           Summary: can't compile empty main in c on hppa 11iv1 (11.11)
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: r dot ford at cox dot net


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


             reply	other threads:[~2007-02-20  6:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20  6:11 r dot ford at cox dot net [this message]
2007-02-20  6:13 ` [Bug c/30868] " r dot ford at cox dot net
2007-02-20  6:39 ` [Bug target/30868] " pinskia at gcc dot gnu dot org
2007-02-23  0:04 ` 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=bug-30868-14126@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).