Re: [GeneX-dev] Tail (2)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Nicolas Bertrand wrote:
> 
> Hi
> 
> I could compile GNU tail from source. I did placed it in /usr/local/bin/
> The script was happier. The installation does not complete:

I think this is because the 1st time you weren;t using the GNU tail (from the text utils) - teh GNU utils have a specific response from the --version query which is how we test for them.

Your compile from scratch seems to have solved that.  Strange that it didn;t complain about the thers tho, unless they DO use the rest of the GNU utils.

ANyway...

> !! System Error:  @ line: 1829  ()

This seems to be a problem with your R distribution; either R did not install properly or the installation script can't find it on the PATH - did your PATH environment variable include R's location?

> !! System Error: No such file or directory @ line: 2190  
> (cd /Users/Shared/Downloads/GeneX-Server-1.0.4/CyberT-dist; R SHLIB runa.c)

See above

> !! System Error: No such file or directory @ line: 2195  
> (cd /Users/Shared/Downloads/GeneX-Server-1.0.4/CyberT-dist; cp hdarray runa.c 
> runa.so /usr/local/genex/lib/R/library/hdarray/R/)

Possibly having to do with the above; if there wasn't a R subdir made, it couldn't copy things to it.  Does '/usr/local/genex/lib/R/library/hdarray/R/' exist?

> !! System Error: No such file or directory @ line: 2498  
> (/usr/bin/perl Makefile.PL)

Hmm - this is odd - it SHOULD do this if you've gotten this far...  
Jason - is there anything in Makefile.PL which would generate this??

> !! System Error: No such file or directory @ line: 2502  (make -s test)

Ditto for Jason.

> !! System Error: No such file or directory @ line: 2507  (make install)

Ditto for Jason.

> !! System Error: No such file or directory @ line: 2631  
> (chmod ug+rw -R /usr/local/genex/rcluster/var/poqs)

this looks like the installation of rcluster stopped prematurely. 
Jason - is this a possibility of the mkdir failing like you mentioned yesterday?
Did '/usr/local/genex/rcluster/var/poqs' get made correctly?  

Thanks for the feedback..

Harry

>   --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                        Name: genex-errors.txt
>    genex-errors.txt    Type: Plain Text (text/plain)
>                    Encoding: 7bit
> 
>   --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> Any ideas?
> 
> Best regards,
> 
> Nicolas
> 
> Begin forwarded message:
> 
> > From: Nicolas Bertrand <nic...@pl...>
> > Date: Wed Nov 14, 2001  11:44:04  Etc/GMT
> > To: gen...@li...
> > Subject:
> >
> > Hello
> >
> > I am installing genex server 1.0.4 on MacOSX10.1. The installation
> > script stalls while checking tail. I was wondering if anybody had such
> > problems.
> >
> >
> > This a snapshot of the installation screen:
> > [...]
> > Testing for a GNU [tail] ...
> > Unknown option: 1
> > Usage: head [-options] <url>...
> >     -m <method>   use method for the request (default is 'HEAD')
> >     -f            make request even if head believes method is illegal
> >     -b <base>     Use the specified URL as base
> >     -t <timeout>  Set timeout value
> >     -i <time>     Set the If-Modified-Since header on the request
> >     -c <conttype> use this content-type for POST, PUT, CHECKIN
> >     -a            Use text mode for content I/O
> >     -p <proxyurl> use this as a proxy
> >     -P            don't load proxy settings from environment
> >     -H <header>   send this HTTP header (you can specify several)
> >
> >     -u            Display method and URL before any response
> >     -U            Display request headers (implies -u)
> >     -s            Display response status code
> >     -S            Display response status chain
> >     -e            Display response headers
> >     -d            Do not display content
> >     -o <format>   Process HTML content in various ways
> >
> >     -v            Show program version
> >     -h            Print this message
> >
> >     -x            Extra debugging output
> > Ugh!  What gibberish!
> > The [tail] you have certainly does not taste like GNU [tail].  If you
> > have
> > a GNU [tail] stashed somewhere in your system, tell me its path below;
> > otherwise cancel (^C) this installation, get a recent version of it from
> > ftp://www.fsf.org/gnu/textutils/
> > compile & install it, then try this installation again.
> > [/usr/bin/tail] ?
> >
> > The man page for version of tail installed is as follows:
> > [localhost:local/bin/xgobi] nicolasb% man tail
> > man: Formatting manual page...
> >
> > TAIL(1)                     System Reference Manual
> > TAIL(1)
> >
> > NAME
> >      tail - display the last part of a file
> >
> > SYNOPSIS
> >      tail [-f | -F | -r] [-b number | -c number | -n number] [file ...]
> >
> > DESCRIPTION
> >      The tail utility displays the contents of file or, by default, its
> > stan-
> >      dard input, to the standard output.
> >
> >      The display begins at a byte, line or 512-byte block location in
> > the in-
> >      put.  Numbers having a leading plus (``+'') sign are relative to
> > the be-
> >      ginning of the input, for example, ``-c +2'' starts the display at
> > the
> >      second byte of the input.  Numbers having a leading minus (``-'')
> > sign or
> >      no explicit sign are relative to the end of the input, for
> > example, ``-n
> >      2'' displays the last two lines of the input.  The default
> > starting loca-
> >      tion is ``-n 10'', or the last 10 lines of the input.
> >
> >      The options are as follows:
> >
> >      -b number
> >              The location is number 512-byte blocks.
> >
> >      -c number
> >              The location is number bytes.
> >
> >      -f      The -f option causes tail to not stop when end of file is
> >              reached, but rather to wait for additional data to be
> > appended to
> >              the input.  The -f option is ignored if the standard input
> > is a
> >              pipe, but not if it is a FIFO.
> >
> >      -F      The -F option is the same as the -f option, except that
> > every
> >              five seconds tail will check to see if the file named on
> > the com-
> >              mand line has been shortened or moved (it is considered
> > moved if
> >              the inode or device number changes) and, if so, it will
> > close the
> >              current file, open the filename given, print out the
> > entire con-
> >              tents, and continue to wait for more data to be appended.
> > This
> >              option is used to follow log files though rotation by
> > newsys-
> >              log(8) or similar programs.
> >
> >      -n number
> >              The location is number lines.
> >
> >      -r      The -r option causes the input to be displayed in reverse
> > order,
> >              by line.  Additionally, this option changes the meaning of
> > the
> >              -b, -c and -n options.  When the -r option is specified,
> > these
> >              options specify the number of bytes, lines or 512-byte
> > blocks to
> >              display, instead of the bytes, lines or blocks from the
> > beginning
> >              or end of the input from which to begin the display.  The
> > default
> >              for the -r option is to display all of the input.
> >
> >      If more than a single file is specified, each file is preceded by
> > a head-
> >      er consisting of the string ``==> XXX <=='' where ``XXX'' is the
> > name of
> >      the file.
> >
> >      The tail utility exits 0 on success, and >0 if an error occurs.
> >
> > BUGS
> >      When using the -F option, tail will not detect a file truncation
> > if, be-
> >      tween the truncation and the next check of the file size, data
> > written to
> >      the file make it larger than the last known file size.
> >
> > SEE ALSO
> >      cat(1),  head(1),  sed(1)
> >
> > STANDARDS
> >      The tail utility is expected to be a superset of the
> > specification.  In
> >      particular, the -b, -r and -F options are extensions to that
> > standard.
> >
> >      The historic command line syntax of tail is supported by this
> > implementa-
> >      tion.  The only difference between this implementation and
> > historic ver-
> >      sions of , once the command line syntax translation has been done,
> > is
> >      that the -b, -c and -n options modify the -r option, i.e. ``-r -c
> > 4''
> >      displays the last 4 characters of the last line of the input,
> > while the
> >      historic tail (using the historic syntax ``-4cr'') would ignore
> > the -c
> >      option and display the last 4 lines of the input.
> >
> > HISTORY
> >      A tail command appeared in Version 7 AT&T UNIX.
> >
> > 4th Berkeley Distribution        June 6,
> > 1993                                2
> >
> >
> ----------------------------------------------
> Nicolas Bertrand
> Department of Plant Sciences
> University of Oxford
> Oxford OX1 3RB
> 
> Tel: ++1865 275 116
> ----------------------------------------------
> >

-- 
Cheers, Harry

Harry J Mangalam -- (949) 856 2847 (v&f) -- man...@ho... 
                    [plain text appreciated]