From: <lange92@2067.resnet.uni.edu>
To: <gcc-help@gcc.gnu.org>
Subject: Re: alias warning
Date: Fri, 03 Aug 2001 01:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0108022146440.30728-100000@2067.resnet.uni.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0108021609410.30728-100000@2067.resnet.uni.edu>
Hello all,
I try to avoid the strange practice of replying to my own posts, but it
looks like I found my answer: the attribute alias is supported in ELF, but
not COFF binaries.
Dan L
On Thu, 2 Aug 2001 lange92@2067.resnet.uni.edu wrote:
> Hi all,
> During the course of my attempt to build gnat/rtems I built a cross
> compiler which produced the following warning:
>
> bspstart.c:215:warning, alias definitions not supported in this
> configuration; ignored
>
> The line in question reads as follows:
>
> void bsp_start (void) __attribute__ ((weak, alias("bsp_start_default")));
>
> Anyone encounter this error before, and/or know how to fix it? I'm working
> with i386-rtemscoff-gcc compiler.
>
> Thanks for any help.
>
> DanL
>
>
prev parent reply other threads:[~2001-08-03 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 19:39 lange92
2001-08-03 1:05 ` lange92 [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=Pine.LNX.4.33.0108022146440.30728-100000@2067.resnet.uni.edu \
--to=lange92@2067.resnet.uni.edu \
--cc=gcc-help@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).