Problems with glibc startup code on the Hurd

[H.J. Lu]

> 
> An other solution is to introduce a new function, let's say
> `__libc_setup_stack', that is called early from `_start'.  On the Hurd
> this function would setup the stack (and most if not all Hurd-specific
> initializations). For Linux(and other ports) it would do nothing.
> `__libc_init_first' would then do the initialization of the library.
> 
> I can provide a patch for such a change, but since changing the
> startup code has a high risk of introducing binary
> incompatibilities. we should really think this over before applying it.
> 

If you do, please add 

#include <sysdep.h>

to start.S and protect __libc_setup_stack with #ifdef/#endif. It will
avoid the dummy call.


-- 
H.J. Lu (hjl@gnu.org)