public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Q@ping.be
To: gcc-gnats@gcc.gnu.org
Subject: other/3340: Build 3.0 on Linux-glibc1 fails: wrong include for syscall.h
Date: Thu, 21 Jun 2001 11:16:00 -0000	[thread overview]
Message-ID: <20010621181151.25803.qmail@sourceware.cygnus.com> (raw)

>Number:         3340
>Category:       other
>Synopsis:       Build 3.0 on Linux-glibc1 fails: wrong include for syscall.h
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 21 11:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Q@ping.be
>Release:        gcc 3.0
>Organization:
>Environment:
Linux libc5
>Description:
I got this error

prims.cc:651: `syscall' undeclared (first use this function)

It includes <sys/syscall.h>, but that contains nothing but some constants.  I changed libjava/include/i386-signal.h to include <syscall.h>, instead of <sys/syscall.h>.
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2001-06-21 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 11:16 Q [this message]
2001-08-18  9:49 rodrigc
2002-11-29 14:22 bangerth

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=20010621181151.25803.qmail@sourceware.cygnus.com \
    --to=q@ping.be \
    --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).