From: "Frank Ch. Eigler" <fche@redhat.com>
To: Steven Bosscher <s.bosscher@student.tudelft.nl>
Cc: gcc@gcc.gnu.org
Subject: Re: Cannot build libmudflap
Date: Tue, 03 Sep 2002 08:26:00 -0000 [thread overview]
Message-ID: <20020903112623.C5661@redhat.com> (raw)
In-Reply-To: <1030960673.762.13.camel@steven>; from s.bosscher@student.tudelft.nl on Mon, Sep 02, 2002 at 11:57:53AM +0200
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Hi -
> I did a bootstrap (tree-ssa-branch, CVS this morning) and all stages
> build fine. But libmudflap doesn't... [...]
>
> /home/steven/devel/gcc/objdir/gcc/xgcc
> -B/home/steven/devel/gcc/objdir/gcc/
> -B/opt/experimental/i586-pc-linux-gnu/bin/
> -B/opt/experimental/i586-pc-linux-gnu/lib/ -isystem
> /opt/experimental/i586-pc-linux-gnu/include -DHAVE_CONFIG_H -I.
> -I../../../gcc/libmudflap -I. -O2 -g -O2 -DWRAP_memset -c
> ../../../gcc/libmudflap/mf-hooks.c -fPIC -DPIC -o .libs/memset-hook.o
> ../../../gcc/libmudflap/mf-hooks.c:316: error: parse error before "__extension__"
> ../../../gcc/libmudflap/mf-hooks.c:316: error: parse error before "__uint8_t"
> ../../../gcc/libmudflap/mf-hooks.c:316: warning: data definition has no type or storage class
> [...]
This appears to come from the inline/macro expansion of memset, on some
gcc/glibc combinations. I'll commit some code to disable this within
libmudflap.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-09-03 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 2:55 Steven Bosscher
2002-09-03 8:26 ` Frank Ch. Eigler [this message]
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=20020903112623.C5661@redhat.com \
--to=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=s.bosscher@student.tudelft.nl \
/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).