Russ, this is my gcc info: gcc version 2.95.3 20010315 (release) MCCALL,DON (HP-USA,ex1) (don_mccall@hp.com) wrote*:> >Hello Russ, >On an HP-UX system, this type of error would mean that you are not using an >ansi c standard compiler - see, if the compiler fails for some reason (it >doesn't like the options it's passed, for instance), then it will fail to >build the little test program that configure is using to test to see if a >particular function is valid on your system. Configure can't tell the >difference between the compiler failing to compile the test program, and the >test program failing - so either way, it marks the function as not >available. >With something as BASIC as seteuid method or automated network interface >stuff failing, its more likely a problem with your compiler. So look at the >config.log file, searching for >"checking for setresuid" > >and see what your compiler is complaining about. Chances are that you need >a later version of gcc for your OS... > >Good luck, >Don >-----Original Message----- >From: Russ Gilman-Hunt [mailto:r_gilman@hotp.com] >Sent: Tuesday, April 09, 2002 6:25 PM >To: Bob Crandell; samba@lists.samba.org >Subject: Re: [Samba] Re: help compiling > > >On Tuesday 09 April 2002 13:57, Bob Crandell wrote: >> I'm new here but I believe this is a no blush zone. >> >> Try ./configure --with-winbind=no >> >> It defaults to being on. >> >Hmm, yes, I see that. In my configure printout, it looks like it decides not > >to build winbind, and then "checks configure summary" and starts complaing >at >that point. (the ./configure --with-winbind=no failed as well, but didn't do > >the 'checking whether to build winbind' thing. ) > >This error has happened to people before (in 1999, for instance): >http://lists.samba.org/pipermail/samba-ntdom/1999-December/041245.html >but I still can't see a way around it. I was kind of hoping it was a common > >mistake / FAQ :) > >-Russ > > >> Russ Gilman-Hunt (r_gilman@hotp.com) wrote*: >> >My kernel looks like this: 2.4.18 >> >and my ./configure is: ./configure *blush* >> > >> >FWIW, I threw all those same flags into my configuration and it died at >> > the same place. >> >> >-------------- >> >checking whether to build winbind... no, no unix domain socket support on >> >linux-gnu >> >checking configure summary >> >WARNING: No automated network interface determination >> >ERROR: no seteuid method available >> >configure: error: summary failure. Aborting config >> >--------------- >> > >> >I don't need to provide secure server services; I need to connect to the >> > file servers at work, that are allegedly available over "windows" shares >> > ( most everyone connects to them via appleshare)... and my previous >> > version of samba died with an error during protocol negotiation. >> > >> >Thanks for your help, Bob! >> > >> >-Russ > > > >