Date: Thu, 23 Mar 95 11:39:03 MST From: terry@cs.weber.edu (Terry Lambert) To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Cc: jkh@freefall.cdrom.com, bde@zeta.org.au, me@tartufo.pcs.dec.com, nate@trout.sri.mt.net, current@FreeBSD.org Subject: Re: Make World Times and a question about shared libs / make all Message-ID: <9503231839.AA19235@cs.weber.edu> In-Reply-To: <199503231759.JAA01346@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Mar 23, 95 09:59:48 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > % cd /usr/include/sys > > % grep "struct foo" *.h > > % cd ../net > > ../net: No such file or directory > > Not possible in current situation. EIther your /usr/include > directory is seriously screwed up, or /usr/src/sys/net is missing. If /usr/include/sys is a symlink to another location, and the parent of the other location does not have a net directory, then since it is a relative cd, it will look up the parent in the link target directory and not get the directory of the link that brought you there. In this particular case, the symling is pointing to /usr/src/sys/sys. And pick something other than 'net', then, like X11. > > % cd .. > > % grep "struct foo" *.h > > No match. > > % ls *.h > > No match. > > % pwd > > /usr/src/sys > > But you had no /usr/src/sys... yea, right... carefull with the > fake scripts. Oh, yes, I did. The problem is in the relative pathing used to go up in the heirarchy resulting in unexpected behaviour. 8-(. When people say that /usr/include should contain symlinks pointing to directories, my teeth begin to itch. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9503231839.AA19235>