Peter Schultz [EMAIL PROTECTED] writes:
Amazing, the obvious. Now I get this:
Hmm, I didn't get any more trouble after I fixed the pragma problem.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of
Wilko Bulte wrote:
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
gcc-3.1 appears to have broken
#pragma weak foo = bar
Wilko
I'm getting the following error on a just built -current, which was a
fresh
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
Wilko Bulte wrote:
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
gcc-3.1 appears to have broken
#pragma weak foo = bar
What's the correct way to do
Alfred Perlstein wrote:
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
Wilko Bulte wrote:
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
gcc-3.1 appears to have broken
#pragma weak foo = bar
#pragma weak foo = bar
What's the correct way to do this now?
I dont know. :-( There are hacks that can work around it, but I think this
is unintentional breakage. I tried changing this:
#pragma weak foo = bar
to
__weak_reference(bar, foo);
void f () __attribute__ ((weak, alias
Alfred Perlstein [EMAIL PROTECTED] writes:
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
gcc-3.1 appears to have broken
#pragma weak foo = bar
What's the correct way to do this now?
#pragma weak foo = bar
as you'd have guessed if you'd bothered to read the error message and
look at
Dag-Erling Smorgrav wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
* Peter Wemm [EMAIL PROTECTED] [020530 01:01] wrote:
gcc-3.1 appears to have broken
#pragma weak foo = bar
What's the correct way to do this now?
#pragma weak foo = bar
as you'd have guessed if you'd
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
I'm getting the following error on a just built -current, which was a
fresh install of 5.0-CURRENT-20020519-JPSNAP:
Yes, and if you'd been reading the mailing list like you're supposed
to you would have already known about this.
I'm getting the following error on a just built -current, which was a
fresh install of 5.0-CURRENT-20020519-JPSNAP:
installing in lib/XThrStub...
rm -f UIThrStubs.o
LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe-ansi -pedantic
-Dasm=__asm
-Wall -Wpointer-arith -I../..
On Wed, May 29, 2002 at 11:38:57PM -0500, Peter Schultz wrote:
FWIW: same here yesterday. I have not yet investigated what's up
Wilko
I'm getting the following error on a just built -current, which was a
fresh install of 5.0-CURRENT-20020519-JPSNAP:
installing in lib/XThrStub...
rm -f
10 matches
Mail list logo