This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/11610] testcases 27_io/* don't work properly remotely
- From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 20 Oct 2003 14:51:20 -0000
- Subject: [Bug libstdc++/11610] testcases 27_io/* don't work properly remotely
- References: <20030720221222.11610.dank@kegel.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11610
------- Additional Comments From bkoz at gcc dot gnu dot org 2003-10-20 14:51 -------
> The right fix would be to use dejagnu's remote file operations
> to copy those files to the target when is_remote is true.
Well, I think the framework tries to copy these files always. See
libstdc++-v3/testsuite/lib/libstdc++.exp
proc v3-init { args } {
...
# Copy any required data files.
v3-copy-files [glob -nocomplain "$srcdir/data/*.tst"] $outdir
v3-copy-files [glob -nocomplain "$srcdir/data/*.txt"] $outdir
...
}
Where
# Called by v3-init below. "Static" to this file.
proc v3-copy-files {srcfiles dstdir} {
foreach f $srcfiles {
if { [catch { set symlink [file readlink $f] } x] } then {
file copy -force $f $dstdir
} else {
if { [regexp "^/" "$symlink"] } then {
file copy -force $symlink $dstdir
} else {
set dirname [file dirname $f]
file copy -force $dirname/$symlink $dstdir
}
}
}
}
If there's a better way to do it, I'm interested in seeing the patch.
best,
benjamin