htdig on windows 2000 _with_ german umlauts

htdig on windows 2000 _with_ german umlauts

[Sasa Velickovic]

Hi.

Has anyone ever done it? Is it possible? I don't know how to eliminate
the Warning: unknown locale!

Cheers 

Sasa Velickovic


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Running Dejagnu under Cygwin

[Cheuk Cheng]

I had installed the gnupro99r1p1 toolkit on my Win2000 machine.  I ran
configure on the parallel source directory of gcc (..\win32\gcc) and then
installed the newly built binaries after make finished.  Then I grabbed
dejagnu-20010126.tar.gz from the web and did the same configure and
installation.  I found there was only a single file called site.exp inside
..\win32\gcc\testsuite while there were lots more subdirectories and files
under the original src\gcc\testsuite directory.  The content of site.exp was
below.


## these variables are automatically generated by make ##
# Do not edit here. If you wish to override these values
# add them to the last section
set rootme "/d/toolchain-x/src-cygnus/gnupro-99r1p1/win32/gcc" (parallel
source directory)
set srcdir "/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/gcc"  (original
source directory)
set host_triplet i686-pc-cygwin32
set build_triplet i686-pc-cygwin32
set target_triplet i686-pc-cygwin32
set target_alias i686-pc-cygwin32
set CFLAGS ""
set CXXFLAGS
"-I/d/toolchain-x/src-cygnus/gnupro-99r1p1/win32/gcc/../libio -I$srcdir/../l
ibg++/src -I$srcdir/../libio -I$srcdir/../libstdc++ -I$srcdir/../libstdc++/s
tl -L/d/toolchain-x/src-cygnus/gnupro-99r1p1/win32/gcc/../libg++ -L/d/toolch
ain-x/src-cygnus/gnupro-99r1p1/win32/gcc/../libstdc++"
append LDFLAGS " -L/d/toolchain-x/src-cygnus/gnupro-99r1p1/win32/gcc/../ld"
set tmpdir /d/toolchain-x/src-cygnus/gnupro-99r1p1/win32/gcc/testsuite
set srcdir "${srcdir}/testsuite"
## All variables above are generated by configure. Do Not Edit ##


If I entered "runtest --tool g++ -srcdir ./testsuite" from win32\gcc\ in
bash, I got the following.

WARNING: Couldn't find the global config file.
Test Run By cheng on Thu Jul 12 12:15:03 2001
Native configuration is i686-pc-cygwin32

                === g++ tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
targe
t.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
ERROR: Couldn't find tool config file for unix.

                === g++ Summary ===

WARNING: g++_version failed:
can't read "GXX_UNDER_TEST": no such variable


If I entered the same command line from src\gcc, I got the following.

WARNING: Couldn't find the global config file.
Test Run By cheng on Thu Jul 12 12:18:59 2001
Native configuration is i686-pc-cygwin

                === g++ tests ===

Schedule of variations:
    unix

Test Run By cheng on Thu Jul 12 12:18:59 2001
Native configuration is i686-pc-cygwin

  === g++ tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using ./testsuite/config/default.exp as tool-and-target-specific interface
file.
Running ./testsuite/g++.dg/special/ecos.exp ...
ALWAYS_CXXFLAGS set to
{additional_flags=-I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++ -I
/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++/stl} ldflags=
incdir=/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/gcc/../include
Executing on host: c++
testsuite/g++.dg/special/conpr-1.C  -finit-priority   -I/d/toolchain-x/src-c
ygnus/gnupro-99r1p1/src/libstdc++ -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/
src/libstdc++/stl -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/gcc/../inclu
de   -lm   -o ./a.out    (timeout = 300)
spawn c++
./testsuite/g++.dg/special/conpr-1.C -finit-priority -I/d/toolchain-x/src-cy
gnus/gnupro-99r1p1/src/libstdc++ -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/s
rc/libstdc++/stl -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/gcc/../includ
e -lm -o ./a.out

PASS: g++.dg/special/conpr-1.C (test for excess errors)
spawn [open ...]

      0 [sig] a.out 1952 open_stackdumpfile: Dumping stack trace to
a.out.stackdump
FAIL: g++.dg/special/conpr-1.C execution test
Executing on host:
++  -finit-priority  -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++
 -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++/stl -I/d/toolchain-
x/src-cygnus/gnupro-99r1p1/src/gcc/../include -c  -o conpr-2a.o
./testsuite/g++.dg/special/conpr-2a.C    (timeout = 300)
spawn
c++ -finit-priority -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++ 
-I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++/stl -I/d/toolchain-x
/src-cygnus/gnupro-99r1p1/src/gcc/../include -c -o conpr-2a.o
./testsuite/g++.dg/special/conpr-2a.C

Executing on host: c++ ./testsuite/g++.dg/special/conpr-2.C

onpr-2a.o -finit-priority  -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/lib
stdc++ -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++/stl -I/d/tool
chain-x/src-cygnus/gnupro-99r1p1/src/gcc/../include   -lm   -o ./a.out
(timeout = 300)
spawn c++ ./testsuite/g++.dg/special/conpr-2.C
conpr-2a.o -finit-priority -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/lib
stdc++ -I/d/toolchain-x/src-cygnus/gnupro-99r1p1/src/libstdc++/stl -I/d/tool
chain-x/src-cygnus/gnupro-99r1p1/src/gcc/../include -lm -o ./a.out

PASS: g++.dg/special/conpr-2.C (test for excess errors)
spawn [open ...]

      0 [sig] a.out 2344 open_stackdumpfile: Dumping stack trace to
a.out.stackdump
FAIL: g++.dg/special/conpr-2.C execution test

<snipped for other tests>

Since I am a novice to GNU, I don't know whether the content of site.exp is
correct or not.  I also don't understand why Dejagnu displays unix as the
running target above, even though sites.exp specifies only i686-pc-cygwin32.
I have read the Dejagnu manual but am confused about how to specify running
Dejagnu and the tests on the same PC.  Does Dejagnu automatically assume
local running or remote running of tests?  If I ran all tests to the end,
the test summary would say that thousands passed while there would tens of
unexpected failures and passes.  At this point, I am not sure whether the
unexpected ones are normal or not.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

mounts in gnupro99r1p1

[Cheuk Cheng]

I am new to GNU and am confused about how to set up device mounts in
general.  I use the following with the Cygwin I recently get from the web.
I also have gnupro99r1p1 installed under d:\cygnus\gnupro99-r1p1.  When I
run the default gnupro.bat file created by the gnupro99r1p1 installer, it
just opens a DOS window within Win2k.  Since the installer put certain
command line tools like ls.exe, bash.exe, etc. under
d:\cygnus\unsupported-99r1\H-i686-cygwin32\bin while other programs like
gcc.exe are placed into d:\cygnus\gnupro-99r1p1\H-i686-cygwin32\bin.  As a
result, entering ls after running bash.exe does not work.  My questions are
what mounts/paths does Cygwin used to locate a tool?  Do I always need to
mount /, /usr/bin, /usr/lib, /usr/local and /usr/cygnus?  What should they
normally be set to (especially gnupro99r1p1 has two different directories
for storing the tools)?

d:\cygnus\latest\bin on /usr/bin type user (binmode)
d:\cygnus\latest\lib on /usr/lib type user (binmode)
d:\cygnus\latest on / type user (binmode)
d:\cygnus\latest on /usr/local type user (textmode)
d:\cygnus\latest on /usr/cygnus type user (binmode)
c:\temps on /tmp type user (textmode)
c: on /c type user (textmode)
d: on /d type user (textmode)
e: on /e type user (textmode)
g: on /g type user (textmode)
k: on /cygdrive/k type user (binmode,noumount)
m: on /cygdrive/m type user (binmode,noumount)
n: on /cygdrive/n type user (binmode,noumount)
u: on /cygdrive/u type user (binmode,noumount)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: mounts in gnupro99r1p1

[Christopher Faylor]

If you have GNUpro 99r1, you probably should also have Red Hat
support, too.  The layout of the tools that were provided in 99r1
are very different from the net release.

Please don't expect support for our commercially provided tools
on this general purpose external mailing list.

If you do not have actual support from Red Hat then you should
just nuke the 99r1 tools and install the net release.

cgf

On Wed, Jul 18, 2001 at 01:16:20PM -0700, Cheuk Cheng wrote:
>I am new to GNU and am confused about how to set up device mounts in
>general.  I use the following with the Cygwin I recently get from the web.
>I also have gnupro99r1p1 installed under d:\cygnus\gnupro99-r1p1.  When I
>run the default gnupro.bat file created by the gnupro99r1p1 installer, it
>just opens a DOS window within Win2k.  Since the installer put certain
>command line tools like ls.exe, bash.exe, etc. under
>d:\cygnus\unsupported-99r1\H-i686-cygwin32\bin while other programs like
>gcc.exe are placed into d:\cygnus\gnupro-99r1p1\H-i686-cygwin32\bin.  As a
>result, entering ls after running bash.exe does not work.  My questions are
>what mounts/paths does Cygwin used to locate a tool?  Do I always need to
>mount /, /usr/bin, /usr/lib, /usr/local and /usr/cygnus?  What should they
>normally be set to (especially gnupro99r1p1 has two different directories
>for storing the tools)?
>
>d:\cygnus\latest\bin on /usr/bin type user (binmode)
>d:\cygnus\latest\lib on /usr/lib type user (binmode)
>d:\cygnus\latest on / type user (binmode)
>d:\cygnus\latest on /usr/local type user (textmode)
>d:\cygnus\latest on /usr/cygnus type user (binmode)
>c:\temps on /tmp type user (textmode)
>c: on /c type user (textmode)
>d: on /d type user (textmode)
>e: on /e type user (textmode)
>g: on /g type user (textmode)
>k: on /cygdrive/k type user (binmode,noumount)
>m: on /cygdrive/m type user (binmode,noumount)
>n: on /cygdrive/n type user (binmode,noumount)
>u: on /cygdrive/u type user (binmode,noumount)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: mounts in gnupro99r1p1

[Cheuk Cheng]

Thanks all for the input.  We had support contract with Red Hat in the past
although I am not sure of the current situation.  Another thing is that we
are using both gnupro99r1p1 and the latest version of Cygwin we download
from the net.  I was originally trying to find out if there were general
guidelines for setting all the mounts regardless of different Cygwin
versions, e.g. /usr/local should point to the parent directory containing
the "bin" directory of the Cygwin tools (although this was only my guess).

-----Original Message-----
From: Christopher Faylor [ mailto:cgf@redhat.com ]
Sent: Wednesday, July 18, 2001 4:29 PM
To: cygwin@cygwin.com
Cc: cheng@powertv.com
Subject: Re: mounts in gnupro99r1p1


If you have GNUpro 99r1, you probably should also have Red Hat
support, too.  The layout of the tools that were provided in 99r1
are very different from the net release.

Please don't expect support for our commercially provided tools
on this general purpose external mailing list.

If you do not have actual support from Red Hat then you should
just nuke the 99r1 tools and install the net release.

cgf

On Wed, Jul 18, 2001 at 01:16:20PM -0700, Cheuk Cheng wrote:
>I am new to GNU and am confused about how to set up device mounts in
>general.  I use the following with the Cygwin I recently get from the web.
>I also have gnupro99r1p1 installed under d:\cygnus\gnupro99-r1p1.  When I
>run the default gnupro.bat file created by the gnupro99r1p1 installer, it
>just opens a DOS window within Win2k.  Since the installer put certain
>command line tools like ls.exe, bash.exe, etc. under
>d:\cygnus\unsupported-99r1\H-i686-cygwin32\bin while other programs like
>gcc.exe are placed into d:\cygnus\gnupro-99r1p1\H-i686-cygwin32\bin.  As a
>result, entering ls after running bash.exe does not work.  My questions are
>what mounts/paths does Cygwin used to locate a tool?  Do I always need to
>mount /, /usr/bin, /usr/lib, /usr/local and /usr/cygnus?  What should they
>normally be set to (especially gnupro99r1p1 has two different directories
>for storing the tools)?
>
>d:\cygnus\latest\bin on /usr/bin type user (binmode)
>d:\cygnus\latest\lib on /usr/lib type user (binmode)
>d:\cygnus\latest on / type user (binmode)
>d:\cygnus\latest on /usr/local type user (textmode)
>d:\cygnus\latest on /usr/cygnus type user (binmode)
>c:\temps on /tmp type user (textmode)
>c: on /c type user (textmode)
>d: on /d type user (textmode)
>e: on /e type user (textmode)
>g: on /g type user (textmode)
>k: on /cygdrive/k type user (binmode,noumount)
>m: on /cygdrive/m type user (binmode,noumount)
>n: on /cygdrive/n type user (binmode,noumount)
>u: on /cygdrive/u type user (binmode,noumount)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: mounts in gnupro99r1p1

[Michael A. Chase]

----- Original Message -----
From: "Cheuk Cheng" <cheng@powertv.com>
To: <cygwin@cygwin.com>
Sent: Wednesday, July 18, 2001 16:42
Subject: RE: mounts in gnupro99r1p1


> Thanks all for the input.  We had support contract with Red Hat in the
past
> although I am not sure of the current situation.  Another thing is that we
> are using both gnupro99r1p1 and the latest version of Cygwin we download
> from the net.  I was originally trying to find out if there were general
> guidelines for setting all the mounts regardless of different Cygwin
> versions, e.g. /usr/local should point to the parent directory containing
> the "bin" directory of the Cygwin tools (although this was only my guess).

I don't think I've seen any rules, but setup.exe only sets /, /usr/bin, and
/usr/lib; everything else is up to you.

I generally create a directories in / then mount each local drive and any
directories or network shares I use a lot to those directories.  You can do
whatever suits you, but I recommend leaving the three mounts created by
setup.exe alone unless you have a very very good reason.

$ mount
d:\cygwin-build\other-src on /usr/src type system (binmode)
d:\cygwin-build on /cygwin-build type system (binmode)
c:\cygwin\bin on /usr/bin type system (binmode)
c:\cygwin\lib on /usr/lib type system (binmode)
c:\cygwin on / type system (binmode)
a: on /a type system (binmode)
c: on /c type system (binmode)
d: on /d type system (binmode)
r: on /cdrom type system (binmode)
v: on /v type system (binmode)
w: on /w type system (binmode)

--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/