Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
problem with emerge dev-libs/mm
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
neil
n00b
n00b


Joined: 30 Jul 2002
Posts: 4

PostPosted: Tue Jul 30, 2002 2:17 am    Post subject: problem with emerge dev-libs/mm Reply with quote

I just set up a gentoo box and everything seemed to go fine. I grabbed a couple packages (ssh, vi) but when I got to apache, I encountered the following error:
Unable to determine maximum shared memory segment size

in /etc/fstab I have
tmpfs /dev/shm tmpfs defaults 0 0

any ideas? here's the complete output of emerge dev-libs/mm


# emerge dev-libs/mm
Calculating dependencies ...done!
>>> emerge dev-libs/mm-1.1.3-r1 to /
>>> md5 ;-) mm-1.1.3.tar.gz
>>> Unpacking source...
>>> Unpacking mm-1.1.3.tar.gz
patching file shtool
>>> Source unpacked.
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Configuring MM (Shared Memory Library), Version 1.1.3 (01-Jul-2000)
Copyright (c) 1999-2000 Ralf S. Engelschall, All Rights Reserved.
Platform: i686-pc-linux-gnu
creating cache ./config.cache

Build Tools:
checking for gcc... gcc
checking whether the C compiler (gcc -march=i686 -O3 -pipe ) works... yes
checking whether the C compiler (gcc -march=i686 -O3 -pipe ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for compilation debug mode... disabled
checking whether make sets ${MAKE}... yes
checking for ranlib... ranlib
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking whether ln -s works... yes
checking for ld used by GCC... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking whether the linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool

Platform Environment:
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for errno.h... yes
checking for limits.h... yes
checking for unistd.h... yes
checking for fcntl.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
decision on mandatory system headers... all fine
checking for memory.h... yes
checking for memcpy... yes
checking for memset... yes
checking for bcopy... yes
checking for _POSIX_PATH_MAX in limits.h... yes
checking for PATH_MAX in limits.h... yes
checking for MAXPATHLEN in sys/param.h... yes
checking for _POSIX_CHILD_MAX in limits.h... yes
checking for CHILD_MAX in limits.h... yes

Virtual Memory Page Size:
checking for unistd.h... (cached) yes
checking for kernel/OS.h... no
checking for getpagesize... yes
checking for sysconf... yes
checking for _SC_PAGESIZE in unistd.h... yes
checking for B_PAGE_SIZE in kernel/OS.h... no
decision on memory page size determination... POSIX.1 sysconf(_SC_PAGESIZE)

Shared Memory Implementation:
checking for sys/mman.h... yes
checking for MAP_ANON in sys/mman.h... yes
checking for mmap... yes
checking for munmap... yes
checking for shm_open... no
checking for shm_unlink... no
checking for /dev/zero... yes
checking for sys/ipc.h... yes
checking for sys/shm.h... yes
checking for sys/file.h... yes
checking for shmget... yes
checking for shmat... yes
checking for shmdt... yes
checking for shmctl... yes
checking for kernel/OS.h... (cached) no
checking for create_area... no
decision on shared memory allocation method... SysV IPC shmget()
checking for shared memory maximum segment size... configure: error: Unable to determine maximum shared memory segment size

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line -140, Exitcode 1
!!! bad ./configure

!!! emerge aborting on /usr/portage/dev-libs/mm/mm-1.1.3-r1.ebuild .
#

thanks,
neil
Back to top
View user's profile Send private message
Naan Yaar
Bodhisattva
Bodhisattva


Joined: 27 Jun 2002
Posts: 1549

PostPosted: Tue Jul 30, 2002 2:45 am    Post subject: Reply with quote

Did you enable SYS V IPC in the General Setup section while compiling your kernel (CONFIG_SYSVIPC=y)?
Back to top
View user's profile Send private message
neil
n00b
n00b


Joined: 30 Jul 2002
Posts: 4

PostPosted: Tue Jul 30, 2002 2:50 am    Post subject: Reply with quote

Naan Yaar wrote:
Did you enable SYS V IPC in the General Setup section while compiling your kernel (CONFIG_SYSVIPC=y)?


yup. I've tried with it enabled and disabled and I get the same results. (interestingly, I get the same 'decision on shared memory allocation method... SysV IPC shmget()' even when SYS V IPC is disabled)

I've also played with the /dev/shm mount with no apparent effect.

I'm poking around my kernel config now, but I'm not seeing what's wrong.
Back to top
View user's profile Send private message
neil
n00b
n00b


Joined: 30 Jul 2002
Posts: 4

PostPosted: Tue Jul 30, 2002 3:15 am    Post subject: Reply with quote

D'OH! I didn't mount my boot partition when I recompiled the kernel... using the *real* kernel mm compiles fine.

thanks!
Back to top
View user's profile Send private message
Naan Yaar
Bodhisattva
Bodhisattva


Joined: 27 Jun 2002
Posts: 1549

PostPosted: Tue Jul 30, 2002 3:26 am    Post subject: Reply with quote

I am not sure how much it will help, but you can unpack the source (it will be in /usr/portage/distfiles/mm-1.1.3.tar.gz) into /tmp and then put an exit at line 2475 in the configure script. This will give you the C file, conftest.c, that is used to obtain the max memory size from shmget. Compiling and running this by hand with additional printf may give you additional clues as to where it fails.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum