fixing up /usr/include

Thread View: comp.sys.next.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by R. Matthew Emerson Sun, 27 Sep 1992 20:17

#1625

Author: R. Matthew Emerson
Date: Sun, 27 Sep 1992 20:17

27 lines
1501 bytes

NeXT's new and "improved" reorganization of /usr/include makes me a bit
grupmy. The main problem is that configuration scripts for software like
perl (not to mention us poor humans) get confused when the header files
aren't in the usual places. 

This little script fixes up /usr/include so it looks more normal.  (well,
normal enough for perl's Configure script to do the right thing.)

# fix up NeXT's 3.0 /usr/include directory

cd /usr/include

ln -s ansi/*.h .
rm errno.h      # errno.h is duplicated in bsd

ln -s bsd/* .
rm m68k machine # don't need these in /usr/include
rm libc.p errno.h # these conflict with precomps

# note: syslog.h is no longer a symlink to sys/syslog.h --- this messes up
# syslog.pl, so you gotta cp <perl-lib>/sys/syslog.ph to <perl-lib>/syslog.ph
# after you run h2ph

Note that errno.h and libc.p must go, or you'll get Very Peculiar errors
when compiling; this is due to the precompiled headers, I believe.

-matt

Re: fixing up /usr/include

#1727

Author: Karsten Thygesen
Date: Sun, 04 Oct 1992 14:30

27 lines
1535 bytes

In article <1992Sep27.201757.22804@cis.ohio-state.edu>  
emerson@hadrosaur.cis.ohio-state.edu (R. Matthew Emerson) writes:
> NeXT's new and "improved" reorganization of /usr/include makes me a bit
> grupmy. The main problem is that configuration scripts for software like
> perl (not to mention us poor humans) get confused when the header files
> aren't in the usual places. 
> 
> This little script fixes up /usr/include so it looks more normal.   
(well,
> normal enough for perl's Configure script to do the right thing.)

Anyone knows if GNU is planning to change their autoconf system to support  
NeXT's new "smart" architecture? There is a LOT of programs which is  
difficult to compile under 3.0 because of this. (like Taylor UUCP, perl  
and more)

Why did they do it?? Before is was a (more or less) clean BSD machine  
(from a Unix point of view), but know it's a...Well..A NeXT..

Karsten.

-- 
Karsten Thygesen (karthy@dannug.dk) (NeXT-Mail welcome)
Danish NeXT Users Group
Phone: +45 98 12 42 59
Aalborg, Denmark.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads