httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: [PATCH] properly clean up linux compilation troubles
Date Sat, 26 Apr 1997 19:09:07 GMT
I looked a the linux kernel code for alpha and it does define SHM_R and
SHM_W, and it does support them.  So I'm not convinced that the user in
#336 had their system properly installed.  I'm finding some people to test
it for me. 

I seem to recall shm stuff being an option in the 1.x kernels... but I've
also been cautioned by the kernel folk that shared memory wasn't very
stable.  So yeah while we might be able to find some define or something,
I don't think it's worth it.  In particular, 2.0.30 is lightyears ahead of
1.x in terms of performance. 

I'll fix the typo.  And support linux 3. 

Dean

On Sat, 26 Apr 1997, Paul Sutton wrote:

> On Sat, 26 Apr 1997, Dean Gaudet wrote:
> > This reverts my LINUX_TWEAK patch, which I am regretting submitting.  It
> > detects linux 1.x and 2.x systems.  For 1.x systems it leaves their conf.h
> > defines the same as 1.2b7 and earlier.  For 2.x systems it defines the
> > HAVE_SHMGET, and HAVE_SYS_RESOURCE_H.  In both cases it leaves
> > USE_FCNTL_SERIALIZED_ACCEPT defined since I don't want to introduce the
> > multiple Listen bug into Linux.
> 
> I agree in principle with this patch (and particularly getting rid of
> LINUX_TWEAK). However didn't PR#336 have the problem that SHMGET did not
> exists on Alpha hardware, although they were using a v2 kernel? Perhaps
> the check in the Configure script should be for
> 
>   i?86-*-linux2
> 
> instead?
> 
> Also if 1.2 might be out there for a long time, isn't it possible there'll
> be a Linux 3 in the future? To make it a bit more future-proof, why not
> check for Linux:[2-9].* instead of just Linux:2.*
> 
> Incidently, I don't seem to have any problems with SHMGET on my Linux
> 1.2.13 system (from a RedHat distribution). If many or most 1.2 and higher
> users are ok with shared memory, but Apache defaults to a file, many
> people will get less than optimum performance. Isn't there any other more
> portable way to check if a _particular_ system has shared memory (e.g.
> look for an include file, try and compile a program with shmget() in it
> and see if it fails)? I think autoconf would be very useful here. 
> 
> Also one little typo:
> 
> Configure:
> > !     *-linux2)
> >   	DEF_WANTHSREGEX=yes
> >   	OS='Linux'
> > ! 	CFLAGS="$CFLAGS -DLINUX=2"
> > ! 	;;
> > !     *-linux1)
> > ! 	DEF_WANTHSREGEX=yes
> > ! 	OS='Linux'
> > ! 	CFLAGS="$CFLAGS -DLINUX=1"
> 
> GuessOS:
> > !     Linux:2.*)
> > ! 	echo "${MACHINE}-whatever-linux2"; exit 0
> > ! 	;;
> > ! 
> > !     Linux:1.*)
> >   	echo "${MACHINE}-whatever-linux"; exit 0
> >   	;;
>                                   ^^^^^^
>                                   linux1
> 
> //pcs
> 
> 
> 


Mime
View raw message