You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Martin Kraemer <Ma...@Mch.SNI.De> on 1999/12/10 10:15:32 UTC
Symlinks [was: [PATCH] MPE/iX apache 1.3.10-dev port take two]
On Thu, Dec 09, 1999 at 10:47:45AM -0700, BIXBY,MARK HP-Cupertino,ex1" wrote:
>
> Recreating the archive with a blocksize of 20 seems to prevent the problem
> from occuring. See attached.
I still get:
% gtar tvzf src-os-mpeix.tar.Z
drwxr-xr-x 270/193 0 Dec 9 18:35 1999 src/os/mpeix/
-rw-r--r-- 270/193 1363 Dec 9 00:58 1999 src/os/mpeix/Makefile.tmpl
-rw-r--r-- 270/193 154 Dec 9 00:58 1999 src/os/mpeix/README
-rw-r--r-- 270/193 4717 Dec 9 00:58 1999 src/os/mpeix/dlopen.c
-rw-r--r-- 270/193 5411 Dec 9 00:58 1999 src/os/mpeix/gettimeofday.c
-rw-r--r-- 270/193 37 Dec 9 00:58 1999 src/os/mpeix/mpe_dl_stub.c
lrwxrwxrwx 270/193 0 Dec 9 18:35 1999 src/os/mpeix/os-inline.c -> ../unix/os-inline.c
lrwxrwxrwx 270/193 0 Dec 9 18:35 1999 src/os/mpeix/os.c -> ../unix/os.c
-rw-r--r-- 270/193 4882 Dec 9 00:58 1999 src/os/mpeix/os.h
Tar: archive /tmp/src-os-mpeix.tar.Z EOF not on block boundary
Exit 3
Looking at the tar archive,...
% gunzip src-os-mpeix.tar
% hd src-os-mpeix.tar | tail
58c0 64 20 2a 2c 20 63 6f 6e 73 74 20 63 68 61 72 20 d *, const char
58d0 2a 29 3b 0a 63 6f 6e 73 74 20 63 68 61 72 20 2a *);.const char *
58e0 61 70 5f 6f 73 5f 64 73 6f 5f 65 72 72 6f 72 28 ap_os_dso_error(
58f0 76 6f 69 64 29 3b 0a 0a 23 65 6e 64 69 66 09 2f void);..#endif./
5900 2a 20 21 41 50 41 43 48 45 5f 4f 53 5f 48 20 2a * !APACHE_OS_H *
5910 2f 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 /...............
5920 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
*
6200 00 .
6201
I see that the archive in fact doesn't end on a block boundary
(1 byte too long!)
But then I tried
% dd if=/dev/zero bs=255 count=1 >>src-os-mpeix.tar
% dd if=/dev/zero bs=10k count=1 >>src-os-mpeix.tar
and finally could extract everything, including os.h
But how should I deal with the symbolic links? While they can
be stored in a tar file, I cannot put them into CVS. Should we
instead add stub files like
---snip---os.c:
#include "../unix/os.c"
---snip---
and
---snip---os-inline.c:
#include "../unix/os-inline.c"
---snip---
or should the symlinks be created dynamically during configure
or make?
Currently, I'd decide in favor of the former.
What do you think?
Martin
--
<Ma...@MchP.Siemens.De> | Fujitsu Siemens
<ma...@apache.org> | 81730 Munich, Germany
Re: Symlinks [was: [PATCH] MPE/iX apache 1.3.10-dev port take two]
Posted by Martin Kraemer <Ma...@Mch.SNI.De>.
On Fri, Dec 10, 1999 at 10:15:32AM +0100, Martin Kraemer wrote:
> But how should I deal with the symbolic links? While they can
> be stored in a tar file, I cannot put them into CVS. Should we
> instead add stub files like
> ---snip---os-inline.c:
> #include "../unix/os-inline.c"
> ---snip---
I just committed your MPE/iX patches together with the stub files
mentionend above. Is that okay with you?
Martin
--
<Ma...@MchP.Siemens.De> | Fujitsu Siemens
<ma...@apache.org> | 81730 Munich, Germany