How about this:
diff --git a/config/distscript.sh b/config/distscript.sh
index d7bdfa4..9f05a2f 100755
--- a/config/distscript.sh
+++ b/config/distscript.sh
@@ -69,7 +69,7 @@ fi
# Trivial helper function
doit() {
echo $*
-$*
+eval $*
}
echo "*** Copying doxygen-doc tree to
Same error.
Brice
Le 07/04/2014 23:43, Jeff Squyres (jsquyres) a écrit :
> How about:
>
> tar c -C /home/ci/hwloc-gitclone -h -f - doc/doxygen-doc | tar x -C
> /home/ci/hwloc-gitclone/build/hwloc-gitclone -f -
>
>
>
> On Apr 7, 2014, at 5:36 PM, Brice Goglin
> wrote:
>
How about:
tar c -C /home/ci/hwloc-gitclone -h -f - doc/doxygen-doc | tar x -C
/home/ci/hwloc-gitclone/build/hwloc-gitclone -f -
On Apr 7, 2014, at 5:36 PM, Brice Goglin
wrote:
> Works on my Linux but fails on Solaris:
> tar -c -C /home/ci/hwloc-gitclone -h -f -
Works on my Linux but fails on Solaris:
tar -c -C /home/ci/hwloc-gitclone -h -f - doc/doxygen-doc | tar -x -C
/home/ci/hwloc-gitclone/build/hwloc-gitclone -f -
tar: /dev/rmt/0: No such file or directory
Le 07/04/2014 23:29, Jeff Squyres (jsquyres) a écrit :
> --- a/config/distscript.sh
> +++
On Apr 7, 2014, at 5:06 PM, "Jeff Squyres (jsquyres)"
wrote:
> Ok, lemme look at tar -- there's a canonical way to copy dir trees with tar;
> let me look it up...
Does this work for you? It seems to do the Right Thing for me on OS X and
Linux.
diff --git
On Apr 7, 2014, at 5:05 PM, Brice Goglin wrote:
> So you just broke my make dist :/
Really? Doh! :-(
> I don't have MacOS to test things. If rsync or tar or whatever can
> dereference symlinks, that'll work for me.
Ok, lemme look at tar -- there's a canonical way to
So you just broke my make dist :/
I don't have MacOS to test things. If rsync or tar or whatever can
dereference symlinks, that'll work for me.
commit 0ebeff689e9414d5eedbf53e7c8697a3af5e4b72
Author: Brice Goglin
List-Post: hwloc-devel@lists.open-mpi.org
Date: Fri Mar
On Apr 7, 2014, at 4:33 PM, Brice Goglin wrote:
> So you're (always?) getting tarballs without any doc/doxygen-doc
> subdirectories?
That's correct -- doc/doxygen-doc is in the source tree, but does not end up in
the tarball.
> Does "make dist" say that it's copying the
So you're (always?) getting tarballs without any doc/doxygen-doc
subdirectories? Does "make dist" say that it's copying the doxygen-doc
subdirectory? Any idea who's removing it later?
I managed to get such a tarball without doc only once, but it
disappeared after I added some debug commands to
Right -- I've done that (i.e., if I do "make doc" again, it does nothing
because it's already done). And "make dist" works fine.
But "make distcheck" fails when it runs "make dist" in the subdir of the
expanded tarball fails because doc/doxygen-doc doesn't exist in there.
On Apr 7, 2014,
In v1.9+, you need make doc before make dist or make distcheck. It may
explain your problem?
I changed this a couple weeks ago to make things much easier to
understand/maintain (but a little bit harder to use :))
Brice
Le 07/04/2014 21:37, Jeff Squyres (jsquyres) a écrit :
> I just pushed
I just pushed 143e27248f928797e2e8532747386c67c9f8d873, which converted
distscript.csh to distscript.sh.
If it works well on master, we can pull it to the v1.9 branch.
I notice that "make distcheck" is broken, however -- when it goes to "make
dist" in the expanded tarball, I get the following
Le 31/03/2014 00:57, Christopher Samuel a écrit :
> On 30/03/14 02:04, Ralph Castain wrote:
>
> > turns out that some linux distro's automatically set LS_COLORS in
> > your environment when running old versions of csh/tcsh via their
> > default dot files
>
> For example RHEL6 does this..
Looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/03/14 02:04, Ralph Castain wrote:
> turns out that some linux distro's automatically set LS_COLORS in
> your environment when running old versions of csh/tcsh via their
> default dot files
For example RHEL6 does this..
- --
Christopher
Jeff just left today for a 1-week vacation. However, this came up on the OMPI
mailing list - turns out that some linux distro's automatically set LS_COLORS
in your environment when running old versions of csh/tcsh via their default dot
files, and it can cause problems with the script. So just
Jeff,
Where does this LS_COLORS variable come from? Who is setting it?
Brice
Le 27/03/2014 11:45, MPI Team a écrit :
> The branch, master has been updated
>via 0e6fe307c10d47efee3fb95c50aee9c0f01bc8ec (commit)
> from 00f85033d269e2c312370bb24043f92a92dff7e3 (commit)
>
> Those
16 matches
Mail list logo