Presence of cygwin64 elements in an existing Cygwin 32 install after updating

Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

Some Cygwin programs are failing even after reboots, re-installing the
faulty program, and the customary automatic rebasing (e.g. 'dig', Line
1 below) after a recent update:

Some cygwin64 packages were installed (see line 17 below (even though
I am running *32* bit cygwin, installed using setup-*x86*.exe:

After the existing setup warned me that there was a newer one, I
downloaded this one before continuing with the update.

    08/23/2017  04:10 PM           871,955 setup-x86.exe

    9afd6a83bbb7dbb55805ab113e1e618e *setup-x86.exe

Lines 1 - 9: After the update I noticed that 'dig' wasn't working
properly (even after a reboot, and a reinstall of the bind-utils
package, and the automatic rebase invoked by 'setup'.)

Lines 12 - 17: cygcheck showed the following note about a missing (64
bit?) cygwin DLL.

Line 17 especially, why is there an 'x86_64' reference on a cygwin 32
bit install?

Lines 20 - 29 show a number of cygwin64 references, 108 to be exact on Line 29:

Line 33 is additional evidence that this is the 32 bit setup program:

Lines 36 - 44 show more info about the setup.ini file.


     1    dig +short -x 127.0.0.1
     2          0 [main] dig (4552) C:\cygwin\bin\dig.exe: *** fatal
error - cygheap base mismatch detected - 0x612E8408/0xBA8408.
     3    This problem is probably due to using incompatible versions
of the cygwin DLL.
     4    Search for cygwin1.dll using the Windows Start->Find/Search facility
     5    and delete all but the most recent version.  The most recent
version *should*
     6    reside in x:\cygwin\bin, where 'x' is the drive on which you have
     7    installed the cygwin distribution.  Rebooting is also suggested if you
     8    are unable to find another cygwin DLL.
     9    Segmentation fault
    10
    11
    12    grep "cygwin1\.dll"
/var/kchristian/cygcheck/cygcheck_s_r_v_20170823_165156
    13     3373k 2017/07/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
    14                      "cygwin1.dll" v0.0 ts=2017-07-12 09:53
    15     3373k 2017/07/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
    16                      "cygwin1.dll" v0.0 ts=2017-07-12 09:53
    17    Missing file:
/usr/x86_64-pc-cygwin/sys-root/usr/bin/cygwin1.dll from package
cygwin64
    18
    19
    20    grep -n cygwin64 /etc/setup/installed.db
    21    543:cygwin64 cygwin64-2.6.0-1.tar.bz2 1
    22    544:cygwin64-binutils cygwin64-binutils-2.25-1.tar.bz2 0
    23    545:cygwin64-binutils-debuginfo
cygwin64-binutils-debuginfo-2.25-1.tar.bz2 1
    24    546:cygwin64-bzip2 cygwin64-bzip2-1.0.6-2.tar.bz2 0
    25    547:cygwin64-catgets cygwin64-catgets-1.1-2.tar.bz2 1
    26
    27
    28    grep -cw cygwin64
"http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
    29    108
    30
    31
    32    ls -l "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
    33    -rwx------+ 1 keith Domain Users 10666707 Aug 23 16:10
http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini
    34
    35
    36    head "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
    37    # This file was automatically generated at 2017-08-22 00:14:06 UTC.
    38    #
    39    # If you edit it, your edits will be discarded next time the file is
    40    # generated.  See http://cygwin.com/setup.html for details.
    41    release: cygwin
    42    arch: x86
    43    setup-timestamp: 1503360846
    44    setup-version: 2.881


Interested in how to remove the cygwin64 components from this cygwin
32 bit system so that failing Cygwin programs work properly.

Thanks!

Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Ken Brown]

On 8/24/2017 9:36 AM, Keith Christian wrote:
> Some Cygwin programs are failing even after reboots, re-installing the
> faulty program, and the customary automatic rebasing (e.g. 'dig', Line
> 1 below) after a recent update:
> 
> Some cygwin64 packages were installed (see line 17 below (even though
> I am running *32* bit cygwin, installed using setup-*x86*.exe:
> 
> After the existing setup warned me that there was a newer one, I
> downloaded this one before continuing with the update.
> 
>      08/23/2017  04:10 PM           871,955 setup-x86.exe
> 
>      9afd6a83bbb7dbb55805ab113e1e618e *setup-x86.exe
> 
> Lines 1 - 9: After the update I noticed that 'dig' wasn't working
> properly (even after a reboot, and a reinstall of the bind-utils
> package, and the automatic rebase invoked by 'setup'.)
> 
> Lines 12 - 17: cygcheck showed the following note about a missing (64
> bit?) cygwin DLL.
> 
> Line 17 especially, why is there an 'x86_64' reference on a cygwin 32
> bit install?
> 
> Lines 20 - 29 show a number of cygwin64 references, 108 to be exact on Line 29:
> 
> Line 33 is additional evidence that this is the 32 bit setup program:
> 
> Lines 36 - 44 show more info about the setup.ini file.
> 
> 
>       1    dig +short -x 127.0.0.1
>       2          0 [main] dig (4552) C:\cygwin\bin\dig.exe: *** fatal
> error - cygheap base mismatch detected - 0x612E8408/0xBA8408.
>       3    This problem is probably due to using incompatible versions
> of the cygwin DLL.
>       4    Search for cygwin1.dll using the Windows Start->Find/Search facility
>       5    and delete all but the most recent version.  The most recent
> version *should*
>       6    reside in x:\cygwin\bin, where 'x' is the drive on which you have
>       7    installed the cygwin distribution.  Rebooting is also suggested if you
>       8    are unable to find another cygwin DLL.
>       9    Segmentation fault
>      10
>      11
>      12    grep "cygwin1\.dll"
> /var/kchristian/cygcheck/cygcheck_s_r_v_20170823_165156
>      13     3373k 2017/07/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>      14                      "cygwin1.dll" v0.0 ts=2017-07-12 09:53
>      15     3373k 2017/07/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>      16                      "cygwin1.dll" v0.0 ts=2017-07-12 09:53
>      17    Missing file:
> /usr/x86_64-pc-cygwin/sys-root/usr/bin/cygwin1.dll from package
> cygwin64
>      18
>      19
>      20    grep -n cygwin64 /etc/setup/installed.db
>      21    543:cygwin64 cygwin64-2.6.0-1.tar.bz2 1
>      22    544:cygwin64-binutils cygwin64-binutils-2.25-1.tar.bz2 0
>      23    545:cygwin64-binutils-debuginfo
> cygwin64-binutils-debuginfo-2.25-1.tar.bz2 1
>      24    546:cygwin64-bzip2 cygwin64-bzip2-1.0.6-2.tar.bz2 0
>      25    547:cygwin64-catgets cygwin64-catgets-1.1-2.tar.bz2 1
>      26
>      27
>      28    grep -cw cygwin64
> "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
>      29    108
>      30
>      31
>      32    ls -l "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
>      33    -rwx------+ 1 keith Domain Users 10666707 Aug 23 16:10
> http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini
>      34
>      35
>      36    head "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
>      37    # This file was automatically generated at 2017-08-22 00:14:06 UTC.
>      38    #
>      39    # If you edit it, your edits will be discarded next time the file is
>      40    # generated.  See http://cygwin.com/setup.html for details.
>      41    release: cygwin
>      42    arch: x86
>      43    setup-timestamp: 1503360846
>      44    setup-version: 2.881
> 
> 
> Interested in how to remove the cygwin64 components from this cygwin
> 32 bit system so that failing Cygwin programs work properly.

The packages whose names start with "cygwin64" are x86 packages intended 
for cross-building 64-bit programs on 32-bit Cygwin.  If you don't want 
them, you can uninstall them in the usual way by running setup-x86.exe. 
I don't think they have anything to do with your problem.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

Thanks, Ken.  Good to know that, I included all troubleshooting info
and methods that I've gleaned from the mailing list over the years.

Maybe the bind-utils maintainer can offer a fix.

Keith

On Thu, Aug 24, 2017 at 8:21 AM, Ken Brown <kbrown@cornell.edu> wrote:
> On 8/24/2017 9:36 AM, Keith Christian wrote:
>>
>> Some Cygwin programs are failing even after reboots, re-installing the
>> faulty program, and the customary automatic rebasing (e.g. 'dig', Line
>> 1 below) after a recent update:
>>
>> Some cygwin64 packages were installed (see line 17 below (even though
>> I am running *32* bit cygwin, installed using setup-*x86*.exe:
>>
>> After the existing setup warned me that there was a newer one, I
>> downloaded this one before continuing with the update.
>>
>>      08/23/2017  04:10 PM           871,955 setup-x86.exe
>>
>>      9afd6a83bbb7dbb55805ab113e1e618e *setup-x86.exe
>>
>> Lines 1 - 9: After the update I noticed that 'dig' wasn't working
>> properly (even after a reboot, and a reinstall of the bind-utils
>> package, and the automatic rebase invoked by 'setup'.)
>>
>> Lines 12 - 17: cygcheck showed the following note about a missing (64
>> bit?) cygwin DLL.
>>
>> Line 17 especially, why is there an 'x86_64' reference on a cygwin 32
>> bit install?
>>
>> Lines 20 - 29 show a number of cygwin64 references, 108 to be exact on
>> Line 29:
>>
>> Line 33 is additional evidence that this is the 32 bit setup program:
>>
>> Lines 36 - 44 show more info about the setup.ini file.
>>
>>
>>       1    dig +short -x 127.0.0.1
>>       2          0 [main] dig (4552) C:\cygwin\bin\dig.exe: *** fatal
>> error - cygheap base mismatch detected - 0x612E8408/0xBA8408.
>>       3    This problem is probably due to using incompatible versions
>> of the cygwin DLL.
>>       4    Search for cygwin1.dll using the Windows Start->Find/Search
>> facility
>>       5    and delete all but the most recent version.  The most recent
>> version *should*
>>       6    reside in x:\cygwin\bin, where 'x' is the drive on which you
>> have
>>       7    installed the cygwin distribution.  Rebooting is also suggested
>> if you
>>       8    are unable to find another cygwin DLL.
>>       9    Segmentation fault
>>      10
>>      11
>>      12    grep "cygwin1\.dll"
>> /var/kchristian/cygcheck/cygcheck_s_r_v_20170823_165156
>>      13     3373k 2017/07/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0
>> sys=4.0
>>      14                      "cygwin1.dll" v0.0 ts=2017-07-12 09:53
>>      15     3373k 2017/07/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0
>> sys=4.0
>>      16                      "cygwin1.dll" v0.0 ts=2017-07-12 09:53
>>      17    Missing file:
>> /usr/x86_64-pc-cygwin/sys-root/usr/bin/cygwin1.dll from package
>> cygwin64
>>      18
>>      19
>>      20    grep -n cygwin64 /etc/setup/installed.db
>>      21    543:cygwin64 cygwin64-2.6.0-1.tar.bz2 1
>>      22    544:cygwin64-binutils cygwin64-binutils-2.25-1.tar.bz2 0
>>      23    545:cygwin64-binutils-debuginfo
>> cygwin64-binutils-debuginfo-2.25-1.tar.bz2 1
>>      24    546:cygwin64-bzip2 cygwin64-bzip2-1.0.6-2.tar.bz2 0
>>      25    547:cygwin64-catgets cygwin64-catgets-1.1-2.tar.bz2 1
>>      26
>>      27
>>      28    grep -cw cygwin64
>> "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
>>      29    108
>>      30
>>      31
>>      32    ls -l
>> "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
>>      33    -rwx------+ 1 keith Domain Users 10666707 Aug 23 16:10
>> http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini
>>      34
>>      35
>>      36    head "http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini"
>>      37    # This file was automatically generated at 2017-08-22 00:14:06
>> UTC.
>>      38    #
>>      39    # If you edit it, your edits will be discarded next time the
>> file is
>>      40    # generated.  See http://cygwin.com/setup.html for details.
>>      41    release: cygwin
>>      42    arch: x86
>>      43    setup-timestamp: 1503360846
>>      44    setup-version: 2.881
>>
>>
>> Interested in how to remove the cygwin64 components from this cygwin
>> 32 bit system so that failing Cygwin programs work properly.
>
>
> The packages whose names start with "cygwin64" are x86 packages intended for
> cross-building 64-bit programs on 32-bit Cygwin.  If you don't want them,
> you can uninstall them in the usual way by running setup-x86.exe. I don't
> think they have anything to do with your problem.
>
> Ken
>
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

Updated to the testing version of cygwin1.dll, rebooted, still seeing
this dig error (updating the cygwin1.dll file may have been
superfluous.)


/home/keith>uname -a
CYGWIN_NT-6.1-WOW windows-machine 2.9.0(0.317/5/3)  i686 Cygwin


/home/keith>>dig +short -x 127.0.0.1
      0 [main] dig (7444) C:\cygwin\bin\dig.exe: *** fatal error -
cygheap base mismatch detected - 0x612EC408/0x84C408.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if you
are unable to find another cygwin DLL.
Segmentation fault

Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

More program failures.  Have rebooted and allowed system to preform rebase:


$ man httping
      0 [main] man 7688 child_info_fork::abort:
C:\cygwin\bin\cygz.dll: Loaded to different address: parent(0x360000)
!= child(0x3E0000)
man: fork failed: Resource temporarily unavailable

Why are all of these programs failing in this way?

Keith


On Tue, Aug 29, 2017 at 11:08 AM, Keith Christian
<keith1christian@gmail.com> wrote:
> Updated to the testing version of cygwin1.dll, rebooted, still seeing
> this dig error (updating the cygwin1.dll file may have been
> superfluous.)
>
>
> /home/keith>uname -a
> CYGWIN_NT-6.1-WOW windows-machine 2.9.0(0.317/5/3)  i686 Cygwin
>
>
> /home/keith>>dig +short -x 127.0.0.1
>       0 [main] dig (7444) C:\cygwin\bin\dig.exe: *** fatal error -
> cygheap base mismatch detected - 0x612EC408/0x84C408.
> This problem is probably due to using incompatible versions of the cygwin DLL.
> Search for cygwin1.dll using the Windows Start->Find/Search facility
> and delete all but the most recent version.  The most recent version *should*
> reside in x:\cygwin\bin, where 'x' is the drive on which you have
> installed the cygwin distribution.  Rebooting is also suggested if you
> are unable to find another cygwin DLL.
> Segmentation fault
>
> Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Eliot Moss]

On 8/29/2017 4:57 PM, Keith Christian wrote:
> More program failures.  Have rebooted and allowed system to preform rebase:
> 
> 
> $ man httping
>        0 [main] man 7688 child_info_fork::abort:
> C:\cygwin\bin\cygz.dll: Loaded to different address: parent(0x360000)
> != child(0x3E0000)
> man: fork failed: Resource temporarily unavailable
> 
> Why are all of these programs failing in this way?

Sometimes I have needed to rebase all programs.  To do this,
do the command: rebase-trigger full
If you're not able to run bash to run this, you can run dash
from Windows CMD and give an explicit path, e.g.,

/cygdrive/c/cygwin/bin/rebase-trigger full

would do the right thin on my installation.  But even that won't
help if you're running 32-bit and have installed too many packages.
There is only so much room in the address space for the various
possible DLLs that might be loaded.

Regards - Eliot Moss

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Marco Atzeri]

On 29/08/2017 23:03, Eliot Moss wrote:
> On 8/29/2017 4:57 PM, Keith Christian wrote:
>> More program failures.  Have rebooted and allowed system to preform 
>> rebase:
>>
>>
>> $ man httping
>>        0 [main] man 7688 child_info_fork::abort:
>> C:\cygwin\bin\cygz.dll: Loaded to different address: parent(0x360000)
>> != child(0x3E0000)
>> man: fork failed: Resource temporarily unavailable
>>
>> Why are all of these programs failing in this way?
> 
> Sometimes I have needed to rebase all programs.  To do this,
> do the command: rebase-trigger full
> If you're not able to run bash to run this, you can run dash
> from Windows CMD and give an explicit path, e.g.,
> 
> /cygdrive/c/cygwin/bin/rebase-trigger full
> 
> would do the right thin on my installation.  But even that won't
> help if you're running 32-bit and have installed too many packages.
> There is only so much room in the address space for the various
> possible DLLs that might be loaded.

Keith,
in addition to Elliot's comment, you can use

   rebase -si

output to  provide an overview of how many dll's are present
and in which address they are mapped.

   $ rebase -si |sort -r --key=5 | head

will provide the list of the one absorbing more address space.
Except the octave-tisean patological case, that I recommend to not 
install if you don't really need it, usually LLVM and ICU
several DLL's are the largest:

  $ rebase -si |sort -r --key=5 | head |awk '{print $5,$1}'
0x020b3000 /usr/bin/cygLLVM-4.0.dll
0x01f75000 /usr/bin/cygQt5WebKit-5.dll
0x01def000 /usr/bin/cygLLVM-3.9.dll
0x01af3000 /usr/bin/cygLLVM-3.8.dll
0x0191d000 /usr/bin/cygicudata59.dll
0x0190a000 /usr/bin/cygicudata58.dll
0x01885000 /usr/bin/cygicudata57.dll
0x017ed000 /usr/bin/cygicudata56.dll
0x01239000 /usr/bin/cyggcj-16.dll
0x00f4f000 /usr/bin/cygoctave-4.dll

Regards
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Eliot Moss]

A query related to this:

If I use rebase -si and look at the range of addresses used, what is
the limit that gets exceeded when I have too many DLLs?  In other words,
what should I look for to determine that I *must* have fewer DLLs?

Regards - Eliot (who uses one ell :-) )

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Marco Atzeri]

On 30/08/2017 14:24, Eliot Moss wrote:
> A query related to this:
> 
> If I use rebase -si and look at the range of addresses used, what is
> the limit that gets exceeded when I have too many DLLs?  In other words,
> what should I look for to determine that I *must* have fewer DLLs?
> 
> Regards - Eliot (who uses one ell :-) )

Ehm, sorry Eliot,

you should look if
- you have collisions ( they are signed by * in rebase -si output)
- if you have very low address as allocation is starting at 0x6fff....
and going down.

In my case, where I have already a large number of package,
but not extreme:

$ cygcheck -cd |wc -l
1639

the lowest address is around 0x36960000

32 $ rebase -si |sort  --key=3 | head| awk '{print $3, $5,$1}'
0x36960000 0x0000b000 /usr/libexec/coreutils/libstdbuf.so
0x36970000 0x00053000 /usr/lib/xorg/modules/extensions/cygglx.dll
0x369d0000 0x0000d000 /usr/lib/xorg/modules/drivers/nested_drv.dll
0x369e0000 0x0000c000 /usr/lib/xorg/modules/drivers/dummy_drv.dll
0x369f0000 0x00031000 /usr/lib/xorg/modules/cygwfb.dll
0x36a30000 0x0000b000 /usr/lib/xorg/modules/cygshadowfb.dll
0x36a40000 0x00011000 /usr/lib/xorg/modules/cygshadow.dll
0x36a60000 0x0000b000 /usr/lib/xorg/modules/cygfbdevhw.dll
0x36a70000 0x00028000 /usr/lib/xorg/modules/cygfb.dll
0x36aa0000 0x0001e000 /usr/lib/xorg/modules/cygexa.dll

marco@GE-MATZERI-EU ~/doc
  32 $ rebase -si |sort  --key=3 | tail | awk '{print $3, $5,$1}'
0x6fc90000 0x00088000 /usr/bin/cygGL-1.dll
0x6fd20000 0x0008a000 /usr/bin/cygFLAC-8.dll
0x6fdb0000 0x00019000 /usr/bin/cygFLAC++-6.dll
0x6fdd0000 0x00034000 /usr/bin/cygEMF-1.dll
0x6fe10000 0x0002a000 /usr/bin/cygEGL-1.dll
0x6fe40000 0x0001a000 /usr/bin/cyg4ti2util-0.dll
0x6fe60000 0x00078000 /usr/bin/cyg4ti2int64-0.dll
0x6fee0000 0x00074000 /usr/bin/cyg4ti2int32-0.dll
0x6ff60000 0x00081000 /usr/bin/cyg4ti2gmp-0.dll
0x6fff0000 0x0000b000 /usr/bin/cyg4ti2common-0.dll

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

Marco (and all:)

I will try the rebase commands.

What are the flags and options for setup-x86.exe to remove all Gnome
and KDE packages?  I run KDE on an adjacent Debian system and removing
it and Gnome on the Windows machine is an option if there are memory
issues.  I install EVERYTHING when I install Cygwin, due to laziness.

I'll run the rebase and other commands shortly.

Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Eliot Moss]

> you should look if
> - you have collisions ( they are signed by * in rebase -si output)

Good tip

> - if you have very low address as allocation is starting at 0x6fff....
> and going down.

I guess I was asking "What is very low?"  My 32-bit installation
currently goes down to 0x3b960000.

In my 64-bit installation it is 0x0003c3c50000.

Would it not be simple to add something to rebase to have it
point out possibly/probably problematic cases?

Regards - Eliot


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Marco Atzeri]

On 30/08/2017 15:09, Keith Christian wrote:
> Marco (and all:)
> 
> I will try the rebase commands.
> 
> What are the flags and options for setup-x86.exe to remove all Gnome
> and KDE packages?  I run KDE on an adjacent Debian system and removing
> it and Gnome on the Windows machine is an option if there are memory
> issues.  I install EVERYTHING when I install Cygwin, due to laziness.
> 
> I'll run the rebase and other commands shortly.
> 
> Keith
> 

On setup "Select Packages" window, choose "View" category,
then on GNOME and/or KDE rows klick multiple times
on "Default" position until you reach "Uninstall"

Regards
Marco

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

Eliot and Marco,

/cygdrive/c/cygwin/bin/rebase-trigger full followed by an install of a
few new packages WORKED.  "dig" and "httping" and other commands now
run properly, thanks!

I'll try the package removal suggestion in a day or so when I have
some time, thanks for that also.

Is there a command line option to remove whold categories, by chance?
I only found instructions for removing individual packages.

Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

Must be this?

C:\Users\keith\Downloads\setup-x86.exe --help

        -c --remove-categories            Specify categories to uninstall

On Wed, Aug 30, 2017 at 11:56 AM, Keith Christian
<keith1christian@gmail.com> wrote:
> Eliot and Marco,
>
> /cygdrive/c/cygwin/bin/rebase-trigger full followed by an install of a
> few new packages WORKED.  "dig" and "httping" and other commands now
> run properly, thanks!
>
> I'll try the package removal suggestion in a day or so when I have
> some time, thanks for that also.
>
> Is there a command line option to remove whold categories, by chance?
> I only found instructions for removing individual packages.
>
> Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Achim Gratz]

Keith Christian writes:
> Must be this?
>
> C:\Users\keith\Downloads\setup-x86.exe --help
>
>         -c --remove-categories            Specify categories to uninstall

Yes.  If in doubt, combine with -M to see what it's up to.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Keith Christian]

Achim,

Thanks, I added -M:

        setup-x86.exe -B -c KDE -M -n -q -v

    Wed 08/30/2017 13:35:26.69 c:\users\keith>Starting cygwin install,
version 2.881
    User has backup/restore rights
    Current Directory: C:\Users\keith\Downloads
    root: C:\cygwin system
    Selected local directory: C:\Users\keith\Downloads
    Found ini file -
C:\Users\keith\Downloads/ftp%3a%2f%2fcygwin.mirrors.pair.com%2f/x86/setup.ini
    INSTALLED.DB version 3

    Found ini file -
C:\Users\keith\Downloads/http%3a%2f%2fcygwin.mirror.constant.com%2f/x86/setup.ini

and got quite a bit of output like this:

    package 4ti2-debuginfo comparing versions 1.6.7-2 and 1.6.7-1, result was 1
    package a2ps comparing versions 4.14-3 and 4.14-3, result was 0
    package a2ps-debuginfo comparing versions 4.14-3 and 4.14-3, result was 0
    package aalib comparing versions 1.4rc5-13 and 1.4rc5-12, result was 1

What is the meaning of "result was 0" and "result was 1" above?

then, another listing similar to this:

    Found category KDE in package akonadi
    Deleted manual package akonadi
    Found category KDE in package amor
    Deleted manual package amor
    Found category KDE in package artikulate
    Deleted manual package artikulate
    Found category KDE in package automoc4
    Deleted manual package automoc4
    Found category KDE in package baloo
    Deleted manual package baloo

What does the above mean?


Are these Perl packages set for removal because they are used by KDE?

    package perl comparing versions 5.22.4-1 and 5.22.1-2, result was 1
    package perl-Algorithm-Diff comparing versions 1.1903-2 and
1.1903-2, result was 0
    package perl-Alien-wxWidgets comparing versions 0.67-2 and 0.67-1,
result was 1
    package perl-Archive-Zip comparing versions 1.59-1 and 1.56-1, result was 1
    package perl-Authen-SASL comparing versions 2.16-2 and 2.16-2, result was 0
    package perl-Authen-SASL-XS comparing versions 1.00-1 and 1.00-1,
result was 0
    package perl-Authen-SASL-XS-debuginfo comparing versions 1.00-1
and 1.00-1, result was 0
    package perl-autovivification comparing versions 0.17-1 and
0.16-1, result was 1
    package perl-autovivification-debuginfo comparing versions 0.17-1
and 0.16-1, result was 1


Finally, I got the setup GUI dialog with a lot of packages that are
set to Uninstall.  I probably won't uninstall until I hear back from
you.  There are a lot of KDE packages listed, and I want to remove
them, but I am interested in answers to my questions first.

Thank you.

Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating

[Achim Gratz]

Keith Christian writes:
> What is the meaning of "result was 0" and "result was 1" above?

It tells you whether the package needs to be updated (1) or not (0).

> then, another listing similar to this:
>
>     Found category KDE in package akonadi
>     Deleted manual package akonadi
>     Found category KDE in package amor
>     Deleted manual package amor
>     Found category KDE in package artikulate
>     Deleted manual package artikulate
>     Found category KDE in package automoc4
>     Deleted manual package automoc4
>     Found category KDE in package baloo
>     Deleted manual package baloo
>
> What does the above mean?

You are deleting all packages in category KDE from the command line
(manually).

> Are these Perl packages set for removal because they are used by KDE?
>
>     package perl comparing versions 5.22.4-1 and 5.22.1-2, result was 1

They are set for update, not removal.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple