public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: egcs@cygnus.com
Subject: Re: OSR5 install of 971031
Date: Mon, 03 Nov 1997 09:43:00 -0000	[thread overview]
Message-ID: <19971103111542.55665@dgii.com> (raw)
In-Reply-To: <17765.878575224@hurl.cygnus.com>

>   > 	The "make install" will call on SCO's /usr/bin/tar if the
>   > PATH variable is not right.  The "tar" in the install needs to
>   > be GNU tar, since it uses a command line switch which is not
>   > recognized by SCO tar.
> Does SCO have cpio?  If so that might be a better choice than
> tar in this situation.

Yes, OpenServer has cpio, as mandated by SVID II and X/Open 1992.
It also provides pax as preferred by X/open 1992.

Though I haven't done a 'make install', it looks like TAROUTOPTS
will choke on the 'B' option, which appears to be a non-standard
extention.

Isn't it jusr really sad that 25+ years later, there isn't a 
portable, efficient, safe way to copy an arbitrary directory 
tree in UNIX?

RJL

  reply	other threads:[~1997-11-03  9:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-03  6:23 Bill Walker
1997-11-03  8:43 ` Jeffrey A Law
1997-11-03  9:43   ` Robert Lipe [this message]
1997-11-03 16:02     ` Jeffrey A Law
1997-11-03 16:27       ` Joern Rennecke
1997-11-04  6:55         ` Jeffrey A Law
1997-11-04  7:38           ` cpio vs. tar. was: " Robert Lipe
1997-11-04 11:52             ` Jeffrey A Law
1997-11-04 17:31               ` teunis
1997-11-04 17:31                 ` Jeffrey A Law
1997-11-04 16:09             ` J. Kean Johnston
1997-11-04 17:02               ` Gavin Koch
1997-11-03  9:43 ` Robert Lipe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19971103111542.55665@dgii.com \
    --to=robertl@dgii.com \
    --cc=egcs@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).