Re: module gethostname

Bruno, On Thu, Sep 16, 2010 at 5:13 PM, Bruno Haible wrote: >> now I get a linking error: >> >> Warning: resolving _gethostname by linking to _gethostn...@8 >> Use --enable-stdcall-fixup to disable these warnings >> Use --disable-stdcall-fixup to disable these fixups >> libgnu_cl.a(sockets.o): In

Re: module gethostname

Sam, > now I get a linking error: > > Warning: resolving _gethostname by linking to _gethostn...@8 > Use --enable-stdcall-fixup to disable these warnings > Use --disable-stdcall-fixup to disable these fixups > libgnu_cl.a(sockets.o): In function `close_fd_maybe_socket': > /cygdrive/c/sds/dev/curr

Re: module gethostname

Bruno Haible wrote: I am now getting undefined reference to `_gethostname_used_without_requesting_gnulib_module_gethostname' This indicates that you have included gnulib , are using gethostname(), and have not asked for the gnulib module 'gethostname'. - If you want

Re: module libposix (was: module gethostname)

Hi Bruce, * Bruce Korb wrote on Thu, Sep 16, 2010 at 08:00:46PM CEST: > 3. config.h needs to be installed. Now, where was that name munger >for the config.h header Thinking of AX_PREFIX_CONFIG_H from the Autoconf Macro Archive? BTW, that currently has a PR (with patch) open against it,

Re: module libposix (was: module gethostname)

Hi Bruno, > On Wed, Sep 15, 2010 at 11:18 AM, Bruno Haible wrote: >> >> Have you tried to follow the approach of >>  ? >> I haven't, but I would like to hear about success or problems that >> you encounter. 1. A

Re: module libposix (was: module gethostname)

Hi Bruno, On Wed, Sep 15, 2010 at 11:18 AM, Bruno Haible wrote: > > Have you tried to follow the approach of >  ? > I haven't, but I would like to hear about success or problems that > you encounter. That should

Re: module gethostname

Bruce, > Once upon a time, long ago and far away, I proposed a new > library, "libcompat" that more-or-less would make all target > platforms look pretty much identical. Lo and behold, over the > past decade, gnulib has gradually grown up to provide all > that infrastructure. The only problem wi

Re: module gethostname

of them, but mingw does not have EWOULDBLOCK in . > I am now getting > > undefined reference to > `_gethostname_used_without_requesting_gnulib_module_gethostname' This indicates that you have included gnulib , are using gethostname(), and have not asked for the gnulib module

Re: module gethostname

On Wed, Sep 15, 2010 at 12:01 PM, Bruce Korb wrote: > So, let's start that discussion again:  let's make an installable > gnulib that basically does all the configure tests for the current > target and cover 99% of all configure runs.  If someone has > a strange configuration with extra libraries

Re: module gethostname

On Wed, Sep 15, 2010 at 10:04 AM, Ralf Wildenhues wrote: > Hi Bruce, > > * Bruce Korb wrote on Wed, Sep 15, 2010 at 07:01:11PM CEST: >> So, let's start that discussion again:  let's make an installable >> gnulib that basically does all the configure tests for the current >> target and cover 99% of

Re: module gethostname

Hi Bruce, * Bruce Korb wrote on Wed, Sep 15, 2010 at 07:01:11PM CEST: > So, let's start that discussion again: let's make an installable > gnulib that basically does all the configure tests for the current > target and cover 99% of all configure runs. How about a config.site file? Cheers, Ralf

Re: module gethostname

On Wed, Sep 15, 2010 at 9:34 AM, Paul Eggert wrote: > On 09/15/2010 08:41 AM, Sam Steingold wrote: >> I have to reiterate my complaint that the gnulib dependencies mean that one >> has >> to include (almost) the whole of gnulib if one includes (almost) any part >> thereof. > > I agree that gnuli

Re: module gethostname

On 09/15/2010 08:41 AM, Sam Steingold wrote: > I have to reiterate my complaint that the gnulib dependencies mean that one > has > to include (almost) the whole of gnulib if one includes (almost) any part > thereof. I agree that gnulib has too many dependencies and I try to remove them when I ca

module gethostname

The only problem which gethostname module fixes is: On mingw, this function has a prototype that differs from that specified by POSIX, and it is defined only in the ws2_32 library. why does it have such extensive dependencies? (sockets! errno!) I have to reiterate my complaint that the gnulib d