Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Nov 1995 11:00:37 -0500 (EST)
From:      Brian Tao <taob@io.org>
To:        Anthony Hill <ahill@interconnect.com.au>
Cc:        Chuck Robey <chuckr@glue.umd.edu>, FREEBSD-PORTS-L <freebsd-ports@FreeBSD.org>
Subject:   Re: The GIMP beta on 2.1.0-RELEASE
Message-ID:  <Pine.BSF.3.91.951128102215.29151b-100000@flinch>
In-Reply-To: <Pine.BSI.3.91.951128230106.16137B-100000@tulpi.interconnect.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Nov 1995, Anthony Hill wrote:
> 
> ld.so: warning: libc.so.2.1: minor version < 2 expected, using it anyway

    Hmmm, my /usr/lib contains these shared libs:

-r--r--r--  1 bin   bin    403106 Jul  3  1994 libc.so.1.1
-r--r--r--  1 bin   bin    466907 Jan 25  1995 libc.so.2.0
-r--r--r--  1 bin   bin    435248 Nov 16 04:40 libc.so.2.2

    I wonder why I have 2.2 and not 2.1 (I'm running 2.1.0-RELEASE)?

> Xlib:  extension "MIT-SHM" missing on display ":0.0".
> Bad system call (core dumped)

    Ah yes... you need the shared memory extensions in your kernel,
and your X server must also support it.  2.1.0 kernels come with the
SysV shared memory, semaphores and message-passing queues enabled by
default.  I should have made note of that in the README.FreeBSD.

    While you're recompiling the kernel, it would be a good idea to
increase the maximum shared memory segment size while you're at it.
The GIMP documentation suggests 32 megabytes (!), and I think FreeBSD
defaults to 4 megabytes (1024 SHMMAXPGS * 4K NBPG size).  Try
increasing SHMMAXPGS to 2048 or 4096 in your kernel config file (seems
safer than changing SHMMAX directly).
--
Brian Tao (BT300, taob@io.org)
Systems Administrator, Internex Online Inc.
"Though this be madness, yet there is method in't"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.951128102215.29151b-100000>