Re: Weak symbols (Was: World breakage in libc_r?)

1999-10-17 Thread John Polstra
In article , <[EMAIL PROTECTED]> wrote: > On 15-Oct-99 at 15:05, John Birrell ([EMAIL PROTECTED]) wrote: > > > A weak symbol is like an alias for another (strong) symbol. The > > linker will link to strong symbols first, then, for any unresolved > > references, i

Re: Weak symbols (Was: World breakage in libc_r?)

1999-10-15 Thread patl
On 15-Oct-99 at 15:05, John Birrell ([EMAIL PROTECTED]) wrote: > On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote: > > Sheer curiosity and most likely a somewhat dim question: > > > > what the h* is a weak versus a strong symbol? > > A weak symbol is like an alias for another (strong)

Weak symbols (Was: World breakage in libc_r?)

1999-10-15 Thread John Birrell
On Fri, Oct 15, 1999 at 08:09:57PM +0200, Wilko Bulte wrote: > Sheer curiosity and most likely a somewhat dim question: > > what the h* is a weak versus a strong symbol? A weak symbol is like an alias for another (strong) symbol. The linker will link to strong symbols first, then, for any unreso

Re: World breakage in libc_r?

1999-10-15 Thread Wilko Bulte
As Daniel Eischen wrote ... Sheer curiosity and most likely a somewhat dim question: what the h* is a weak versus a strong symbol? Thanks, Wilko > John Birrell wrote: > > Weak symbols don't work too well _between_ libraries. If libc is linked > > before libpthread, any unresolved refer

Re: World breakage in libc_r?

1999-10-15 Thread David O'Brien
> On a related topic, we should fix the Alpha to emit the weak alias > like the i386 does. We should do what ever is reasonably possible to keep these two archs operating the same. IMHO, people will expect their FreeBSD platform knowledge to hold on the Alpha. -- -- David([EMAIL PROTECTED]

Re: World breakage in libc_r?

1999-10-14 Thread Daniel Eischen
John Birrell wrote: > Weak symbols don't work too well _between_ libraries. If libc is linked > before libpthread, any unresolved references when libc is searched will > use the weak symbols from there, regardless of the fact that a strong > symbol exists in libpthread. If libc is linked after lib

Re: World breakage in libc_r?

1999-10-14 Thread John Birrell
On Thu, Oct 14, 1999 at 05:35:05PM -0400, Daniel Eischen wrote: > One of the things on my wish list is a libpthread that can be linked > with libc. So the way to accomplish this is to have null hooks with > weak symbols in libc, and provide the same (non-null) functions in > libpthread but with s

Re: World breakage in libc_r?

1999-10-14 Thread John Polstra
> John Polstra wrote: > > One of the things on my wish list is a libpthread that can be linked > with libc. So the way to accomplish this is to have null hooks with > weak symbols in libc, and provide the same (non-null) functions in > libpthread but with strong symbols? Oh, maybe, but be carefu

Re: World breakage in libc_r?

1999-10-14 Thread Daniel Eischen
John Polstra wrote: > I know now why it worked on the i386 but not on the Alpha. On the > i386 a system call "read", for example, produces a strong (normal > global) symbol "_read" and a weak alias "read". Because the symbols > were weak, the linker didn't complain about the multiple definitions

Re: World breakage in libc_r?

1999-10-14 Thread John Birrell
On Thu, Oct 14, 1999 at 02:06:40PM -0700, John Polstra wrote: > On a related topic, we should fix the Alpha to emit the weak alias > like the i386 does. That's for ANSI/ISO C compliance, so that if a > user defines his own version of read(), it won't affect the behavior > of, say, getc(). We nee

Re: World breakage in libc_r?

1999-10-14 Thread John Polstra
In article <[EMAIL PROTECTED]>, Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > Doug Rabson wrote: > > On Wed, 13 Oct 1999, John Polstra wrote: > > > > > and the fix is to add sigpending.o and sigsuspend.o to the > > > definition of HIDDEN_SYSCALLS in "src/lib/libc_r/Makefile". > > > > > > > I'm

Re: World breakage in libc_r?

1999-10-14 Thread Daniel Eischen
Kenneth Wayne Culver wrote: > Speaking of libc_r, (this is unrelated sort of) I was wondering if anyone > was planning on adding the pthread_setcancel and other pthread cancel > stuff to -CURRENT. I was trying to use it the other day when I realized it > wasn't there... :-) Just a question, I'm n

Re: World breakage in libc_r?

1999-10-14 Thread Kenneth Wayne Culver
Speaking of libc_r, (this is unrelated sort of) I was wondering if anyone was planning on adding the pthread_setcancel and other pthread cancel stuff to -CURRENT. I was trying to use it the other day when I realized it wasn't there... :-) Just a question, I'm not demanding anything. ===

Re: World breakage in libc_r?

1999-10-14 Thread Wilko Bulte
As John Polstra wrote ... > I'm building world on an Alpha and have run into this: > > building shared library libc_r.so.4 > sigpending.So: In function `sigpending': > sigpending.S:2: multiple definition of `sigpending' > uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here >

Re: World breakage in libc_r?

1999-10-14 Thread Marcel Moolenaar
Doug Rabson wrote: > > On Wed, 13 Oct 1999, John Polstra wrote: > > > building shared library libc_r.so.4 > > sigpending.So: In function `sigpending': > > sigpending.S:2: multiple definition of `sigpending' > > uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here > > /usr/ob

Re: World breakage in libc_r?

1999-10-14 Thread Doug Rabson
On Wed, 13 Oct 1999, John Polstra wrote: > I'm building world on an Alpha and have run into this: > > building shared library libc_r.so.4 > sigpending.So: In function `sigpending': > sigpending.S:2: multiple definition of `sigpending' > uthread_sigpending.So(.text+0x0):uthread_sigpending.c: firs

World breakage in libc_r?

1999-10-13 Thread John Polstra
I'm building world on an Alpha and have run into this: building shared library libc_r.so.4 sigpending.So: In function `sigpending': sigpending.S:2: multiple definition of `sigpending' uthread_sigpending.So(.text+0x0):uthread_sigpending.c: first defined here /usr/obj/a/src/tmp/usr/libexec/elf/ld: