Date: Thu, 27 Apr 2006 13:55:06 -0400
From: Derrell.Lipman@UnwiredUniverse.com
To: libc-alpha@sourceware.org
Subject: Re: fopen() calls __open()
Message-ID: <vesux5s5.fsf@oberon-mail.internal>
References: <vesvx8jj.fsf@oberon-mail.internal> <4450F946.6030909@redhat.com>
	<8xprx810.fsf@oberon-mail.internal> <445102AC.5090505@redhat.com>
MIME-Version: 1.0

Ulrich Drepper <drepper@redhat.com> writes:

> Derrell.Lipman@UnwiredUniverse.com wrote:
>> I'm a bit confused as to why certain functions are weak and allowed to be
>> overridden (e.g. open, __open)
>
> Forget about weak.  The is no difference in the treatment of weak and
> strong symbols when they are defined in DSOs.  They are all the same.
> The aspect interesting for you is exported or not.  No internal libc
> call except those to the malloc functions references names which are
> exported.

Ok.  So that means that if I want applications running over the Samba wrapper
(smbsh) to be able to call fopen() and have them open files on the remote
Windows server as currently works with open() and __open(), I need to put an
implementation of fopen() and friends into the LD_PRELOAD library as well.
I'm not looking forward to lugging around all that extra code, but it sounds
like that's my only choice.

If you have any other suggestions for me, I'd certainly like to hear them!

Thanks for your help,

Derrell