public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/25936]  New: FAIL: libgomp.c/appendix-a/a.15.1.c (test for excess errors)
Date: Tue, 24 Jan 2006 00:03:00 -0000	[thread overview]
Message-ID: <bug-25936-276@http.gcc.gnu.org/bugzilla/> (raw)

Executing on host: /mnt/gnu/gcc-3.3/objdir/gcc/xgcc
-B/mnt/gnu/gcc-3.3/objdir/gc
c/ /mnt/gnu/gcc-3.3/gcc/libgomp/testsuite/libgomp.c/appendix-a/a.15.1.c 
-B/mnt/
gnu/gcc-3.3/objdir/hppa64-hp-hpux11.11/./libgomp/
-I/mnt/gnu/gcc-3.3/objdir/hppa
64-hp-hpux11.11/./libgomp -I/mnt/gnu/gcc-3.3/gcc/libgomp/testsuite/..
-fmessage-
length=0 -fopenmp  -O2 -fopenmp  
-L/mnt/gnu/gcc-3.3/objdir/hppa64-hp-hpux11.11/
./libgomp/.libs -lgomp -lm   -o ./a.15.1.exe    (timeout = 300)
ld: (Warning) Unsatisfied symbol "sem_init" in file
/mnt/gnu/gcc-3.3/objdir/hppa
64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
ld: (Warning) Unsatisfied symbol "sem_post" in file
/mnt/gnu/gcc-3.3/objdir/hppa
64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
ld: (Warning) Unsatisfied symbol "sem_wait" in file
/mnt/gnu/gcc-3.3/objdir/hppa
64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
ld: (Warning) Unsatisfied symbol "sem_destroy" in file
/mnt/gnu/gcc-3.3/objdir/h
ppa64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
4 warnings.
output is:
ld: (Warning) Unsatisfied symbol "sem_init" in file
/mnt/gnu/gcc-3.3/objdir/hppa
64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
ld: (Warning) Unsatisfied symbol "sem_post" in file
/mnt/gnu/gcc-3.3/objdir/hppa
64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
ld: (Warning) Unsatisfied symbol "sem_wait" in file
/mnt/gnu/gcc-3.3/objdir/hppa
64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
ld: (Warning) Unsatisfied symbol "sem_destroy" in file
/mnt/gnu/gcc-3.3/objdir/h
ppa64-hp-hpux11.11/./libgomp/.libs/libgomp.sl
4 warnings.

FAIL: libgomp.c/appendix-a/a.15.1.c (test for excess errors)

I'm not sure what's going on here.  While the header files and manpages seem
to indicate the presence of POSIX semaphores, they seem missing from the
libraries.


-- 
           Summary: FAIL: libgomp.c/appendix-a/a.15.1.c (test for excess
                    errors)
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
 GCC build triplet: hppa64-hp-hpux11.11
  GCC host triplet: hppa64-hp-hpux11.11
GCC target triplet: hppa64-hp-hpux11.11


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


             reply	other threads:[~2006-01-24  0:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24  0:03 danglin at gcc dot gnu dot org [this message]
2006-01-24  0:59 ` [Bug libgomp/25936] " pinskia at gcc dot gnu dot org
2006-01-24  2:12 ` dave at hiauly1 dot hia dot nrc dot ca
2006-01-29 20:26 ` [Bug libgomp/25936] libgomp needs to link against rt on HPUX pinskia at gcc dot gnu dot org
2006-02-08 17:46 ` roger at eyesopen dot com
2006-02-08 18:17 ` dave at hiauly1 dot hia dot nrc dot ca
2006-02-13  2:33 ` sayle at gcc dot gnu dot org
2006-02-13 19:02 ` roger at eyesopen dot com

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-25936-276@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).