[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] Make test failure on Cygwin
From: |
John Meinel |
Subject: |
Re: [Gnu-arch-users] Make test failure on Cygwin |
Date: |
Tue, 06 Jul 2004 19:45:17 -0500 |
User-agent: |
Mozilla Thunderbird 0.7.1 (Windows/20040626) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ron Parker wrote:
| On Tue, 06 Jul 2004 18:23:31 -0500, John Meinel <address@hidden>
wrote:
|
|
|>Ron Parker wrote:
|>| On Tue, 06 Jul 2004 15:46:30 -0500, John Meinel <address@hidden>
|>wrote:
|
|
| That may seem odd to the rest of the world, but may be a reasonable
| compromise. For that matter, I don't think sed even needs the no-op
| replacement. A command with a null script should work, "sed ''".
I was trying to figure out sed's no-op. Because just plain "sed" doesn't
work. And "sed 's///'" doesn't either.
|
|
|
|>| I don't think it would be using the wrong version because an explicit
|>| ../libexec path should be getting used to exec them. However, as I
|>| previously mentioned I have not checked to see if it might be using a
|>| stale version that already exists from a previous install.
|
|
| Small typo, s/\.\./\.\.\./. IOW, the .. was intended as an ellipsis,
| "...". I was trying to asy it would use the fully qualified path that
| includes the libexec sub directory.
|
But doesn't that mean it won't work for "make test"? Because it's
"hard-coded" inside the tla binary to look for ".../libexec/tar".
|
|>Where does it decide "../libexec"? I know the "make test" command has an
|>explicit path to the tla to run, does tla internally call
|>popen("../libexec/tar ...")?
|
|
| I'd have to grep the source and this isn't my machine, but I remember
| archive.h contains some of the cfg_... macros that are used.
|
| (oops, cut your question about my archive and gmail doesn't have a
deep undo.)
|
| Yes, this is in my archive. Specifically, check patch-4.
|
|
|>Well, what I'd like to see is that the Makefile.in files do exist in the
|>source repository. Makefile.am can be used to generate it, but that
|>should be done by you, it shouldn't be necessary to have autotools
|>installed to build the project.
|
|
| Granted. I intended to get around to this, but was trying to keep my
| initial commits down to what was simply needed to support the
| pathcompression. Since I am sharing this with other I wil go ahead
| and reconf my archive. But, I'm fairly wiped from travelling and
| intend to just unwind tonight. Maybe I will have time to check it in
| before work tomorrow.
|
| I was also thinking about what I could trim from the archive. I will
| give this more thought later.
|
No problem. Enjoy your evening.
|
|>Actually, from what I was seeing, the autotools screwed up more than
|>they helped (probably because I have a different version.) If I tried to
|>play around with any of the Makefile.* files it would try to re-generate
|>and then my build would fail. If I just did a fresh checkout, configure,
|>build, then things would work. And if I only changed hackerlab I could
|>type make again and it would work.
|
|
| BTW, my autotools are just the newest from Cygwin setup.
I'm guessing that's what mine are as well, though I can re-run setup to
make sure. I just know that running "autoconf" in the tar directory gave
me warnings about missing macros.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA60edJdeBCYSNAAMRAuwYAJ9xuLftrWiGAOkiQxz59xP5h0uDGACfUpCC
eZcS/jxOjKVSL/PBxARvsCo=
=hVCv
-----END PGP SIGNATURE-----
- [Gnu-arch-users] Make test failure on Cygwin, John Meinel, 2004/07/05
- Re: [Gnu-arch-users] Make test failure on Cygwin, Ron Parker, 2004/07/06
- Re: [Gnu-arch-users] Make test failure on Cygwin, John Meinel, 2004/07/06
- Re: [Gnu-arch-users] Make test failure on Cygwin, Ron Parker, 2004/07/06
- Re: [Gnu-arch-users] Make test failure on Cygwin,
John Meinel <=
- Re: [Gnu-arch-users] Make test failure on Cygwin, Ron Parker, 2004/07/07