Re: Setup feature request: adding a Skipped view

2003-01-30 Thread Max Bowsher
To Brian: cygwin-apps is the preferred place to discuss setup development.
Transferring this thread there.

To cygwin-apps: Here is a patch from Brian Keener which got forgotten.
It adds 2 additional views, Only Keeps and Only Skips. I think this could be
valuable, and these very features are in the setup todo list.


Max.


Brian Keener wrote:
 Actually the last change I submitted at Roberts request was against
 HEAD (at the time) and can be found at:
 http://sources.redhat.com/ml/cygwin-patches/2002-q3/msg00110/ViewChng

 The actual discussion on the change and my posting of the change
 begins with message:

 http://sources.redhat.com/ml/cygwin-patches/2002-q3/msg00080.html

 on July 12 2002.




Re: Serious error compiling setup

2003-01-30 Thread Brian Keener
Max Bowsher wrote:
  When I try to compile setup I get the following:
  
  + /usr/develop/src/cygwin-apps/setup/configure -C
  --enable-dependencies --disable-shared --host=i686-pc-mingw32 
  --build=i686-pc-cygwin CC=gcc -mno-cygwin CXX=g++ -mno-cygwin 
  CPPFLAGS=-I/usr/include/g++-3 --enable-maintainer-mode
 
 Drop the CPPFLAGS bit, that dates back to gcc-2.95.3

ok

  checking for C++ compiler default output... configure: error: C++
  compiler cannot create executables
 
 gcc-mingw package?

Yes but i have reinstalled it and gcc several times and still no better

  check `config.log' for details.
 
 Well?

See below

  In addition to the above I also receive while compiling setup a
  dialog box titled 16bit MS-DOS SubSystem with the message:
  g++
  The NTVDM CPU has encountered an illegal instruction.
  CS:067f IP:017d OP:ff ff 75 13 8b CHoose 'Close' to terminate the
  application. 
 
 DJGPP?

???

  Having failed with setup I decided to try to compile cygwin I there I
  get the following error:
  
  + /usr/develop/src/configure --enable-debugging --build=i686=pc-cygwin
  --target=i686-pc-cygwin --enable-haifa --prefix=/usr --exec-prefix=/usr
  --sysconfdir=/etc --libdir=/usr/lib --includedir=/nonexistent/include
  configure: error: cannot run /bin/bash /usr/develop/src/config.sub
 
 How about some elementary troubleshooting of the error? 
 Like: Does it exist, check permissions?

This was the result of a bad merge that I missed the result .# File on.  I 
usually check for these.  In this case the merge code was still there along 
with some other files that still had merge code.  I cleaned them up, still 
could not get to compile and reinstalled gcc and gcc-mingw and deleted all my 
source config* files and Make* files and reupdated from cvs to get them back.  
Still no luck.

When I try to configure setup (not build, just  configure) I get this on the 
screen still even after the above:

+ /usr/develop/src/cygwin-apps/setup/configure -C --enable-dependencies 
--disabl
e-shared --host=i686-pc-mingw32 --build=i686-pc-cygwin CC=gcc -mno-cygwin 
CXX=g+
+ -mno-cygwin --enable-maintainer-mode
configure: loading cache config.cache
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for i686-pc-mingw32-strip... no
checking for strip... strip
checking whether to enable maintainer-specific portions of Makefiles... yes
checking Whether to build inilint... no
checking Whether to enable rsync support... no
checking for i686-pc-mingw32-g++... g++ -mno-cygwin
checking for C++ compiler default output... configure: error: C++ compiler 
canno
t create executables
check `config.log' for details.
~
$

In checking the config.log now it would appear the pertinent part is:

configure:2044: checking for C++ compiler default output
configure:2047: g++ -mno-cygwinconftest.cc  5
g++: installation problem, cannot exec 
`/usr/lib/gcc-lib/i686-pc-mingw32/3.2/../
./../../i686-pc-mingw32/bin/ld.exe': Invalid argument
configure:2050: $? = 1
configure: failed program was:
#line 2027 configure
#include confdefs.h

int
main ()
{

  ;
  return 0;
}
configure:2077: error: C++ compiler cannot create executables
check `config.log' for details.


Yes i686-pc-mingw32 exists and contains 3 directories which are linked to other 
directories.  The bin directory is linked to ../i686-pc-cygwin/bin and in this 
directory there is an ld.exe and all users have execute privilige.


When I try to configure the build for cygwin (not even build it) I get this on 
the screen:

+ /usr/develop/src/configure --enable-debugging --host=i686-pc-cygwin 
--build=i6
86-pc-cygwin --target=i686-pc-cygwin --enable-haifa --prefix=/usr 
--exec-prefix=
/usr --sysconfdir=/etc --libdir=/usr/lib --includedir=/nonexistent/include
loading cache ./config.cache
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking build system type... i686-pc-cygwin

and the process hangs.  If I check the Process stack from another window 
running rxvt and a bash shell I get this:

$ ps -ef 
 UID PIDPPID TTY STIME COMMAND
  briank1328   1   1  11:06:30 /usr/bin/bash
  BrianK 584   1   0  11:06:22 /usr/bin/rxvt
  briank1692 584   2  11:06:35 /usr/bin/bash
  briank17801328   1  11:06:44 /usr/bin/sh
  briank18001780   1  11:06:45 /usr/bin/sh
  briank18281800   1  11:06:56 /usr/bin/gcc
  briank19001828   1  11:06:57 /usr/i686-pc-cygwin/bin/as
  briank14121692   2  11:14:01 /usr/bin/ps
~
$ 

The above I have to kill manually and if I check the config.log I simply see 
the following:

$ less config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:578: checking host system type
configure:599: checking target system type
configure:617: checking 

Re: What is killing my links (.lnk)

2003-01-30 Thread Brian Keener
Christopher Faylor wrote:
 On Wed, Jan 29, 2003 at 08:04:25PM -0500, Brian Keener wrote:
 Does anyone have any idea why my links are disappearing or probably better 
 phrased as being broken.
 
 I don't know this is happening but this isn't the mailing list for
 exploring the problem.

Well, in reviewing my original post I see I failed to mention that what I was 
actually inquiring into was whether or not the update of packages via setup on 
a Win2k system could be causing these broken links.  Cygwin-apps is the place 
we discuss setup correct???

Since the only thing I have done of late with my copy of cygwin is keep the 
packages updated and update my sources and occasionally recompile, I have a 
feeling that there might be something in setup turning of the read only flag 
and not turning it back on which seems to be breaking the link.

Just a thought.  If with my clarification I am still in the wrong mailing list, 
my apologies and if no one else has run into this then it must be something on 
my system and again my apologies.

bk





Re: Serious error compiling setup

2003-01-30 Thread Max Bowsher
Brian Keener wrote:
 Max Bowsher wrote:
 gcc-mingw package?

 Yes but i have reinstalled it and gcc several times and still no
 better

 In addition to the above I also receive while compiling setup a
 dialog box titled 16bit MS-DOS SubSystem with the message:
 g++
 The NTVDM CPU has encountered an illegal instruction.
 CS:067f IP:017d OP:ff ff 75 13 8b CHoose 'Close' to terminate the
 application.

 DJGPP?

 ???

A DOS port of gcc. Best guess is what Chris has already said: Your g++ is
corrupt. But you said you had reinstalled. Weird. Is there possibly another
g++ (not Cygwin) in the PATH first?

 When I try to configure setup (not build, just  configure) I get this
 on the screen still even after the above:

 checking for i686-pc-mingw32-g++... g++ -mno-cygwin
 checking for C++ compiler default output... configure: error: C++
 compiler canno
 t create executables
 check `config.log' for details.

 In checking the config.log now it would appear the pertinent part is:

 configure:2044: checking for C++ compiler default output
 configure:2047: g++ -mno-cygwinconftest.cc  5
 g++: installation problem, cannot exec
 `/usr/lib/gcc-lib/i686-pc-mingw32/3.2/../
 ./../../i686-pc-mingw32/bin/ld.exe': Invalid argument
 configure:2050: $? = 1
 configure: failed program was:
 #line 2027 configure
 #include confdefs.h

 int
 main ()
 {

   ;
   return 0;
 }
 configure:2077: error: C++ compiler cannot create executables

 Yes i686-pc-mingw32 exists and contains 3 directories which are
 linked to other directories.  The bin directory is linked to
 ../i686-pc-cygwin/bin and in this directory there is an ld.exe and
 all users have execute privilige.


 When I try to configure the build for cygwin (not even build it) I
 get this on the screen:

 + /usr/develop/src/configure --enable-debugging --host=i686-pc-cygwin
 --build=i6
 86-pc-cygwin --target=i686-pc-cygwin --enable-haifa --prefix=/usr
 --exec-prefix=
 /usr --sysconfdir=/etc --libdir=/usr/lib
 --includedir=/nonexistent/include loading cache ./config.cache
 checking host system type... i686-pc-cygwin
 checking target system type... i686-pc-cygwin
 checking build system type... i686-pc-cygwin

 and the process hangs.  If I check the Process stack from another
 window running rxvt and a bash shell I get this:

 $ ps -ef
  UID PIDPPID TTY STIME COMMAND
   briank1328   1   1  11:06:30 /usr/bin/bash
   BrianK 584   1   0  11:06:22 /usr/bin/rxvt
   briank1692 584   2  11:06:35 /usr/bin/bash
   briank17801328   1  11:06:44 /usr/bin/sh
   briank18001780   1  11:06:45 /usr/bin/sh
   briank18281800   1  11:06:56 /usr/bin/gcc
   briank19001828   1  11:06:57 /usr/i686-pc-cygwin/bin/as
   briank14121692   2  11:14:01 /usr/bin/ps
 ~
 $

 The above I have to kill manually and if I check the config.log I
 simply see the following:

 $ less config.log
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.

 configure:578: checking host system type
 configure:599: checking target system type
 configure:617: checking build system type
 config.log (END)

  Thanks for any assistance

It sounds as if your system is very very messed up. I suggest totally
removing and reinstalling Cygwin.


Max.




Re: What is killing my links (.lnk)

2003-01-30 Thread Max Bowsher
Brian Keener wrote:
 Christopher Faylor wrote:
 On Wed, Jan 29, 2003 at 08:04:25PM -0500, Brian Keener wrote:
 Does anyone have any idea why my links are disappearing or probably
 better phrased as being broken.

 I don't know this is happening but this isn't the mailing list for
 exploring the problem.

 Well, in reviewing my original post I see I failed to mention that
 what I was actually inquiring into was whether or not the update of
 packages via setup on a Win2k system could be causing these broken
 links.  Cygwin-apps is the place we discuss setup correct???

Yes... but I don't think that this can be caused by setup. It's used by many
many people without problems.

Coupled with your other problems, I can only believe that your problem is
deeper than Cygwin goes. I'd try a full reinstall of Cygwin. If you have no
luck with that... then it is nothing to do with Cygwin - maybe time to
reinstall Windows?

 Since the only thing I have done of late with my copy of cygwin is
 keep the packages updated and update my sources and occasionally
 recompile, I have a feeling that there might be something in setup
 turning of the read only flag and not turning it back on which seems
 to be breaking the link.

No, can't think of any way setup could do that.

 Just a thought.  If with my clarification I am still in the wrong
 mailing list, my apologies and if no one else has run into this then
 it must be something on my system and again my apologies.

Its looking like some weird condition unique to your system.

Max.




Re: What is killing my links (.lnk)

2003-01-30 Thread Brian Keener
Max Bowsher wrote:
 Its looking like some weird condition unique to your system.

Thanks for both your responses, I'll keep digging and as you say - may have to 
try a full install of cygwin again. 

Bk





RE: Integrating Ralf's rebase into setup.exe

2003-01-30 Thread Ralf Habacker
 The attached fixes the following:
 
 1. merge problem when you applied (by hand?) the following patch:
 
http://cygwin.com/ml/cygwin/2002-12/msg00138.html
 
 2. bug I introduced in the above patch when I attempted but did
not successfully fix rebasing up
 
 #1 causes the base address to be an extra DLL size amount lower and #2
 causes the base address to be an extra DLL size amount higher.
 
Applied and checked in. 


Ralf