Re: FreeBSD 5.3 setup help

Hi there,

On 03/02/2005, at 10:06 PM, Chris Vetter wrote:

>> Either way, what I'm interested in finding out is whether there are  
>> any
>> suggestions people might have for adjusting the Makefile(s) for  
>> FreeBSD
>> ports so that GNUstep will install smoothly without this /proc  
>> problem.
>
> Apparently, the problem seems to be related to FreeBSD 5.3 only
> (I may be wrong, but I do not have the problem on 5.2).
>
> The actual problem is indeed in libkvm, which, under certain
> circumstances DOES need a working /proc (actually, it's just one
> particular function, kvm_uread() called from kvm_doargv() under some
> conditions, that needs /proc).
>
> So, until Pascal Hofstee can provide a fix to libkvm, the only way
> right now seems to be the installation of procfs and mounting /proc.

Right, so could someone in the meantime add a note regarding this for  
the Platform Specific instructions for FreeBSD 5.x?
http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep- 
howto_6.html#SEC21

i.e.,
___Instead of Just saying___
Tested on 5.0 and 5.1
Recommended compiler
Extra libs needed
None.

Special Instructions
Can install via /usr/ports/devel/gnustep, but not all required  
dependancies are installed. See the GNUstep-HOWTO for list of  
libraries.

___Insert Instructions for 5.3___
Two things to try:
1/ type (as root):
mount_procfs proc /proc

-or-

2/ add this line to /etc/fstab and reboot:
proc	/proc	procfs	rw	0	0

See 'man mount_std' and/or 'man procfs'

then install via /usr/ports/devel/gnustep

Now move onto Section #4 of the GNUstep Installation Instructions.
----------------------------------------

I assume that option #2 is the preferred assuming that proc is needed  
after install.
Thanks to Andy Farkas (from the FreeBSD [email protected] list)

I've just done option #2 and then...
	 cd /usr/ports/devel/gnustep && make install clean

...and all of the dependencies seemed to install without a hitch. (See  
list of final output below if anyone notices anything missing - that  
would be good to know :)

Cheers.

with regards,

--
Lachlan Deck

<...>
===> Registering installation for gnustep-back-0.9.4
===> Returning to build of gnustep-1.10.0
===> Generating temporary packing list
===> Checking if devel/gnustep already installed
===> Registering installation for gnustep-1.10.0
===> Cleaning for libaudiofile-0.2.6
===> Cleaning for libiconv-1.9.2_1
===> Cleaning for autoconf-2.59_2
===> Cleaning for bison-1.75_2
===> Cleaning for ffcall-1.10
===> Cleaning for gettext-0.14.1
===> Cleaning for gmake-3.80_2
===> Cleaning for gnustep-make-1.10.0
===> Cleaning for imake-6.8.1
===> Cleaning for libtool-1.3.5_2
===> Cleaning for libtool-1.5.10
===> Cleaning for m4-1.4.1
===> Cleaning for p5-gettext-1.03
===> Cleaning for pkgconfig-0.15.0_1
===> Cleaning for jpeg-6b_3
===> Cleaning for libungif-4.1.3
===> Cleaning for png-1.2.8_1
===> Cleaning for tiff-3.7.1_2
===> Cleaning for gcc-objc-3.3.6_20050112
===> Cleaning for gnustep-base-1.10.1
===> Cleaning for perl-5.8.6
===> Cleaning for libgmp-4.1.4
===> Cleaning for help2man-1.34.2
===> Cleaning for freetype2-2.1.7_4
===> Cleaning for expat-1.95.8
===> Cleaning for libxml2-2.6.17
===> Cleaning for libxslt-1.1.12_1
===> Cleaning for fontconfig-2.2.3,1
===> Cleaning for libXft-2.1.6
===> Cleaning for gnustep-back-0.9.4
===> Cleaning for gnustep-gui-0.9.4
===> Cleaning for xorg-libraries-6.8.1_1
===> Cleaning for gnustep-1.10.0