Re: Curious problem with man FIXED but Alliance install is BROKEN

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2008-08-13 at 21:39 -0700, jdow wrote:
> From: "jdow" <jdow@xxxxxxxxxxxxx>
> Sent: Wednesday, 2008, August 13 19:24
> 
> 
> > F8
> > "man man" does not find anything.
> > "man -M /usr/share/man man" finds the man file for man just fine.
> > Directory permissions look fine. Config files are identical with
> > another F8 machine.
> > ===8<---
> > [root@thing ~]# man -d man
> > Reading config file /etc/man.config
> > found man directory /usr/share/man
> > found man directory /usr/local/man
> > found man directory /usr/local/share/man
> > found man directory /usr/X11R6/man
> > found manpath map /bin --> /usr/share/man
> > found manpath map /sbin --> /usr/share/man
> > found manpath map /usr/bin --> /usr/share/man
> > found manpath map /usr/sbin --> /usr/share/man
> > found manpath map /usr/local/bin --> /usr/local/share/man
> > found manpath map /usr/local/sbin --> /usr/local/share/man
> > found manpath map /usr/X11R6/bin --> /usr/X11R6/man
> > found manpath map /usr/bin/X11 --> /usr/X11R6/man
> > found manpath map /usr/bin/mh --> /usr/share/man
> > 
> > using /usr/bin/less -is as pager
> > 
> > using /usr/bin/less -is as browser
> > 
> > using /bin/cat to dump HTML pages as text
> > adding /usr/lib/alliance/man to manpath
> ^^^^^^^^^^^^^ magic line ^^^^^^^^^^^^^^^^
> > No manual entry for man
> 
> After considerable digging I found a series of errors with the
> alliance-libs installation.
> 
> ===8<--- From the end of alc_env.sh
> # System environment variables.
>  PATH=$PATH:$ALLIANCE_TOP/bin:
>  export PATH
> 
> # Only needed on Solaris (included in /etc/ld.so.conf under Linux).
>  if [ -z "${LD_LIBRARY_PATH}" ]; then
>    LD_LIBRARY_PATH=$ALLIANCE_TOP/lib
>  else
>    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ALLIANCE_TOP/lib:
>  fi
>  export LD_LIBRARY_PATH
> 
>  if [ -z "${MANPATH}" ]; then
>    MANPATH=$ALLIANCE_TOP/man
>  else
>    MANPATH=$MANPATH:$ALLIANCE_TOP/man:
>  fi
>  export MANPATH
> 
> # fixing *** ERROR *** : Variable MBK_SPI_MODEL not found.
>   MBK_SPI_MODEL=$ALLIANCE_TOP/etc/spimodel.cfg;      export MBK_SPI_MODEL
> 
> ===8<--- Below works AND even gives the alliance man entries.
> # System environment variables.
>  PATH=$PATH:$ALLIANCE_TOP/bin
>  export PATH
> 
> # Only needed on Solaris (included in /etc/ld.so.conf under Linux).
>  if [ -z "${LD_LIBRARY_PATH}" ]; then
>    LD_LIBRARY_PATH=$ALLIANCE_TOP/lib
>  else
>    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ALLIANCE_TOP/lib
>  fi
>  export LD_LIBRARY_PATH
> 
> # if [ -z "${MANPATH}" ]; then
> #   MANPATH=$ALLIANCE_TOP/man
> # else
> #   MANPATH=$MANPATH:$ALLIANCE_TOP/man
> # fi
> # export MANPATH
> 
> # fixing *** ERROR *** : Variable MBK_SPI_MODEL not found.
>   MBK_SPI_MODEL=$ALLIANCE_TOP/etc/spimodel.cfg;      export MBK_SPI_MODEL
> ===8<---
> 
> Note the extra colons.
> 
> ALso note the definition of MANPATH which overrides the settings in
> /etc/man.config. If the alliance people are reading the list maybe they
> will get the message. I didn't see an address on their website for bugs.
> 
> Maybe if somebody else gets curious about laying out VLSI tools and
> installs Alliance they might find this and learn why man died.
----
posting this on the list might satisfy yourself but a bugzilla entry has
the potential of solving this problem for others.

Craig

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux