* package _version_ check
@ 2003-09-09 18:22 Sam Steingold
2003-09-09 18:58 ` Max Bowsher
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Sam Steingold @ 2003-09-09 18:22 UTC (permalink / raw)
To: cygwin
how do I check that the installed package foo was built against cygwin
1.5 and not 1.3?
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
An elephant is a mouse with an operating system.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 18:22 package _version_ check Sam Steingold
@ 2003-09-09 18:58 ` Max Bowsher
2003-09-09 19:40 ` Sam Steingold
2003-09-09 19:02 ` Igor Pechtchanski
2003-09-09 20:00 ` Lapo Luchini
2 siblings, 1 reply; 12+ messages in thread
From: Max Bowsher @ 2003-09-09 18:58 UTC (permalink / raw)
To: sds, cygwin
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Sam Steingold wrote:
> how do I check that the installed package foo was built against cygwin
> 1.5 and not 1.3?
I've attached a perl script (CVID - Cygwin Version IDentify) that I wrote,
which you can run on an .exe or .dll.
It examines "objdump -p" output (so requires binutils), and deduces the API
based on which functions the the exe/dll imports from cygwin1.dll.
new = 1.5.x
old = 1.3.x
mixed = the peculiar brokenness early in the 1.5.x series
immune = *Possibly* independent of the changed datatype. Investigate all
dependent DLLs.
Max.
[-- Attachment #2: cvid.pl --]
[-- Type: application/octet-stream, Size: 2444 bytes --]
#!/usr/bin/perl
use strict;
use warnings 'all' => 'FATAL';
use diagnostics;
my @oldfuncs = qw( open acl aclcheck aclfrommode aclfrompbits aclfromtext aclsort acltomode acltopbits acltotext chown facl fchown fdopen fgetpos fopen freopen fseeko fsetpos fstat ftello ftruncate getegid geteuid getgid getgrent getgrgid getgrnam getgroups getpwuid getpwuid_r getuid initgroups lchown lseek lstat mknod mmap seekdir setegid seteuid setgid setgroups setregid setreuid setuid stat telldir truncate );
my @newfuncs = qw( _open64 _acl32 _aclcheck32 _aclfrommode32 _aclfrompbits32 _aclfromtext32 _aclsort32 _acltomode32 _acltopbits32 _acltotext32 _chown32 _facl32 _fchown32 _fdopen64 _fgetpos64 _fopen64 _freopen64 _fseeko64 _fsetpos64 _fstat64 _ftello64 _ftruncate64 _getegid32 _geteuid32 _getgid32 _getgrent32 _getgrgid32 _getgrnam32 _getgroups32 _getpwuid32 _getpwuid_r32 _getuid32 _initgroups32 _lchown32 _lseek64 _lstat64 _mknod32 _mmap64 _seekdir64 _setegid32 _seteuid32 _setgid32 _setgroups32 _setregid32 _setreuid32 _setuid32 _stat64 _telldir64 _truncate64 );
my (%is_old, %is_new);
@is_old{ @oldfuncs } = (1) x @oldfuncs;
@is_new{ @newfuncs } = (1) x @newfuncs;
sub idver($)
{
-f($_) or return "ERR";
undef $/;
open(FH, "objdump -p \"".$_[0]."\" |") or die;
my $odmp = <FH>;
close(FH);
$odmp =~ m/(^The Import Tables.*?)(^\S|\Z)/ms or die;
$odmp = $1;
$odmp =~ m/^\s*DLL Name: cygwin1\.dll$(.*?)^\s*$/ms or return "non-cyg";
my @imps = split /\n/, $1;
$_ = shift @imps; m/^\s*$/ or die "Unexpected: \'$_\'\n";
$_ = shift @imps; m/vma: / or die "Unexpected: \'$_\'\n";
my ($has_old, $has_new);
foreach (@imps)
{
m/^\s*(\S+)\s+(\S+)\s+(\S+)\s*$/ or die;
$has_old = 1 if $is_old{$3};
$has_new = 1 if $is_new{$3};
}
my $type;
if ($has_old and $has_new) { $type = "mixed"; }
elsif ($has_old) { $type = "old"; }
elsif ($has_new) { $type = "new"; }
else { $type = "immune"; }
my @dlls = grep { m/^\s*DLL Name: (?!cygwin1)/ } split(/\n/, $odmp);
@dlls = map { m/^\s*DLL Name: (?:cyg)?(.*?)(?:\.dll|\.DLL)?$/; $1; } @dlls;
my %dlls;
@dlls{@dlls} = (1)x@dlls;
for (qw(
ADVAPI32
COMCTL32
COMDLG32
GDI32
IMM32
KERNEL32
NETAPI32
OLE32
SHELL32
USER32
WINSPOOL.DRV
)) { delete $dlls{$_}; }
@dlls = keys %dlls;
return $type . " (" . join(' ', @dlls).")";
};
for (@ARGV)
{
print $_.": ".idver($_)."\n";
}
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 18:22 package _version_ check Sam Steingold
2003-09-09 18:58 ` Max Bowsher
@ 2003-09-09 19:02 ` Igor Pechtchanski
2003-09-09 19:14 ` Sam Steingold
2003-09-09 20:00 ` Lapo Luchini
2 siblings, 1 reply; 12+ messages in thread
From: Igor Pechtchanski @ 2003-09-09 19:02 UTC (permalink / raw)
To: Sam Steingold; +Cc: cygwin
On Tue, 9 Sep 2003, Sam Steingold wrote:
> how do I check that the installed package foo was built against cygwin
> 1.5 and not 1.3?
I doubt there's a utility that'd tell you that. At a guess, if you only
want to distinguish between these two versions, you should be able to call
"strings" on an executable from the package and look at the bottom for
functions added in Cygwin 1.5, but that's only going to tell you if the
package is using new functionality or not.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 19:02 ` Igor Pechtchanski
@ 2003-09-09 19:14 ` Sam Steingold
2003-09-09 19:25 ` Igor Pechtchanski
0 siblings, 1 reply; 12+ messages in thread
From: Sam Steingold @ 2003-09-09 19:14 UTC (permalink / raw)
To: cygwin
> Igor Pechtchanski <crpugpun@pf.alh.rqh> [Tue, 9 Sep 2003 15:02:25 -0400 (EDT)]:
> On Tue, 9 Sep 2003, Sam Steingold wrote:
>
> > how do I check that the installed package foo was built against cygwin
> > 1.5 and not 1.3?
>
> I doubt there's a utility that'd tell you that. At a guess, if you
> only want to distinguish between these two versions, you should be
> able to call "strings" on an executable from the package and look at
> the bottom for functions added in Cygwin 1.5, but that's only going to
> tell you if the package is using new functionality or not.
shouldn't setup.exe refuse to install 1.5.3 unless all packages that
use 1.3 are also upgraded? like RPM and apt-get at al do?!
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
The early bird may get the worm, but the second mouse gets the cheese.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 19:14 ` Sam Steingold
@ 2003-09-09 19:25 ` Igor Pechtchanski
2003-09-09 20:37 ` Sam Steingold
0 siblings, 1 reply; 12+ messages in thread
From: Igor Pechtchanski @ 2003-09-09 19:25 UTC (permalink / raw)
To: Sam Steingold; +Cc: cygwin
On Tue, 9 Sep 2003, Sam Steingold wrote:
> > Igor Pechtchanski <crpugpun@pf.alh.rqh> [Tue, 9 Sep 2003 15:02:25 -0400 (EDT)]:
> > On Tue, 9 Sep 2003, Sam Steingold wrote:
> >
> > > how do I check that the installed package foo was built against cygwin
> > > 1.5 and not 1.3?
> >
> > I doubt there's a utility that'd tell you that. At a guess, if you
> > only want to distinguish between these two versions, you should be
> > able to call "strings" on an executable from the package and look at
> > the bottom for functions added in Cygwin 1.5, but that's only going to
> > tell you if the package is using new functionality or not.
>
> shouldn't setup.exe refuse to install 1.5.3 unless all packages that
> use 1.3 are also upgraded? like RPM and apt-get at al do?!
I think you got it backwards. Cygwin 1.5 will run pre-1.5 programs with
no problems. It's when you get a program compiled for 1.5 with an older
DLL (e.g., 1.3.22) that you have a problem.
FWIW, setup.ini syntax supports versioned requirements. I don't think
"upset" (the tool that's used to generate setup.ini on the mirrors) does.
Setup itself currently does not support them either, IIRC.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 18:58 ` Max Bowsher
@ 2003-09-09 19:40 ` Sam Steingold
2003-09-09 19:49 ` Christopher Faylor
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Sam Steingold @ 2003-09-09 19:40 UTC (permalink / raw)
To: cygwin
> Max Bowsher <znko@hxs.arg> [Tue, 9 Sep 2003 19:58:39 +0100]:
> Sam Steingold wrote:
> > how do I check that the installed package foo was built against cygwin
> > 1.5 and not 1.3?
>
> I've attached a perl script (CVID - Cygwin Version IDentify) that I wrote,
> which you can run on an .exe or .dll.
> It examines "objdump -p" output (so requires binutils), and deduces the API
> based on which functions the the exe/dll imports from cygwin1.dll.
>
> new = 1.5.x
> old = 1.3.x
> mixed = the peculiar brokenness early in the 1.5.x series
> immune = *Possibly* independent of the changed datatype. Investigate all
> dependent DLLs.
cool! thanks!
$ for f in `find / -name \*.exe -o -name \*.dll`; do ~/bin/cvid.pl $f; done > check
find: . changed during execution of find
Use of uninitialized value in pattern match (m//) at
/cygdrive/d/sds//bin/cvid.pl line 27 (#1)
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl tells you what operation
you used the undefined value in. Note, however, that perl optimizes your
program and the operation displayed in the warning may not necessarily
appear literally in your program. For example, "that $foo" is
usually optimized into "that " . $foo, and the warning will refer to
the concatenation (.) operator, even though there is no . in your
program.
Use of uninitialized value in pattern match (m//) at
/cygdrive/d/sds//bin/cvid.pl line 28 (#1)
Use of uninitialized value in concatenation (.) or string at
/cygdrive/d/sds//bin/cvid.pl line 28 (#1)
Uncaught exception from user code:
Unexpected: ''
main::idver('undef') called at /cygdrive/d/sds//bin/cvid.pl line 69
187 binaries (out of 637) are marked as "old". yuk.
$ for f in `grep old check|cut -f1 -d:`; do cygcheck -f $f; done|sort -u
bc-1.06-1
bison-20030307-1
byacc-1.9-1
compface-1.4-5
ctags-5.5-4
dpkg-1.10.4-2
ed-0.2-1
enscript-1.6.3-3
expat-1.95.6-1
findutils-4.1.7-4
flex-2.5.4-2
fortune-1.8-2
gcc-3.2-3
gdbm-1.8.3-7
ghostscript-7.05-2
gnupg-1.2.2-1
gperf-2.7.2-1
grace-5.1.12-1
grep-2.5-1
groff-1.18.1-2
gzip-1.3.3-4
indent-2.2.8-1
libbz2_0-1.0.2-1
libdb3.1-3.1.17-2
libdb3.1-devel-3.1.17-2
libgdbm-1.8.0-5
libgdbm3-1.8.3-3
libguile12-1.6.0-1
libguile12abi13-1.6.4-2
libguile14-1.5.6-5
libintl-0.10.38-3
libintl1-0.10.40-1
libkpathsea3abi13-2.0.2-2
libncurses5-5.2-1
libncurses6-5.2-8
libpopt0-1.6.4-4
libreadline4-4.1-2
libtiff3-3.6.0-2
libxml2-2.5.7-1
libxslt-1.0.30-2
links-0.96-1
m4-1.4-1
make-3.80-1
man-1.5j-2
mc-4.6.0-4
more-2.11o-1
nasm-0.98.37-1
ncftp-3.1.4-1
openssl096-0.9.6j-1
patchutils-0.2.22-2
perl-5.8.0-5
postgresql-7.3.4-2
psutils-1.17-1
rsync-2.5.6-1
texinfo-4.2-4
textutils-2.0.21-1
tidy-030201-1
time-1.7-1
units-1.77-1
upx-1.24-1
wget-1.8.2-2
whois-4.6.2-1
it would be very nice if the above packages were re-built against 1.5
I am getting spurious failures, and I would love to have them fixed.
thanks!
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
((lambda (x) (list x (list 'quote x))) '(lambda (x) (list x (list 'quote x))))
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 19:40 ` Sam Steingold
@ 2003-09-09 19:49 ` Christopher Faylor
2003-09-09 20:41 ` Sam Steingold
2003-09-09 20:18 ` Max Bowsher
2003-09-10 4:48 ` Charles Wilson
2 siblings, 1 reply; 12+ messages in thread
From: Christopher Faylor @ 2003-09-09 19:49 UTC (permalink / raw)
To: cygwin
On Tue, Sep 09, 2003 at 03:40:41PM -0400, Sam Steingold wrote:
>it would be very nice if the above packages were re-built against 1.5
Pay attention. There is no need to rebuild packages against 1.5. Old
applications work fine modulo the usual bugs that crop in with any new
release. The hoopla and concern about 1.5.x is just FUD.
>I am getting spurious failures, and I would love to have them fixed.
"spurious failures", eh? Yeah, we'll get right on that.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam@sourceware.org
and be permanently blocked from mailing lists at sources.redhat.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 18:22 package _version_ check Sam Steingold
2003-09-09 18:58 ` Max Bowsher
2003-09-09 19:02 ` Igor Pechtchanski
@ 2003-09-09 20:00 ` Lapo Luchini
2 siblings, 0 replies; 12+ messages in thread
From: Lapo Luchini @ 2003-09-09 20:00 UTC (permalink / raw)
To: CygWin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sam Steingold wrote:
| how do I check that the installed package foo was built against
| cygwin 1.5 and not 1.3?
"strings"ing and "grep"ing it for "64" should do the trick.
e.g. rsync-2.5.6-2 (1.5.x verisonm9 contains:
$ strings /usr/bin/rsync.exe | grep 64
_fopen64
_fstat64
_lseek64
_lstat64
_open64
_stat64
_fopen64
_fstat64
_lseek64
_lstat64
_open64
_stat64
while rsync-2.5.6-1 does not.
- --
Lapo 'Raist' Luchini
lapo@lapo.it (PGP & X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAj9eMW8ACgkQaJiCLMjyUvtAkwCeIuUiSSSx5E17pmJQqDCXjL2P
yysAoNCCGQondALrxzE5VwUkl/mFAWPl
=Awco
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 19:40 ` Sam Steingold
2003-09-09 19:49 ` Christopher Faylor
@ 2003-09-09 20:18 ` Max Bowsher
2003-09-10 4:48 ` Charles Wilson
2 siblings, 0 replies; 12+ messages in thread
From: Max Bowsher @ 2003-09-09 20:18 UTC (permalink / raw)
To: sds, cygwin
Sam Steingold wrote:
>> Max Bowsher <znko@hxs.arg> [Tue, 9 Sep 2003 19:58:39 +0100]:
>> I've attached a perl script (CVID - Cygwin Version IDentify) that I
wrote,
>> which you can run on an .exe or .dll.
>> It examines "objdump -p" output (so requires binutils), and deduces the
API
>> based on which functions the the exe/dll imports from cygwin1.dll.
>>
>> new = 1.5.x
>> old = 1.3.x
>> mixed = the peculiar brokenness early in the 1.5.x series
>> immune = *Possibly* independent of the changed datatype. Investigate all
>> dependent DLLs.
>
> cool! thanks!
>
> $ for f in `find / -name \*.exe -o -name \*.dll`; do ~/bin/cvid.pl $f;
done >
...
> 187 binaries (out of 637) are marked as "old". yuk.
>
> $ for f in `grep old check|cut -f1 -d:`; do cygcheck -f $f; done|sort -u
> bc-1.06-1
> bison-20030307-1
> byacc-1.9-1
> compface-1.4-5
> ctags-5.5-4
> dpkg-1.10.4-2
> ed-0.2-1
> enscript-1.6.3-3
> expat-1.95.6-1
> findutils-4.1.7-4
> flex-2.5.4-2
> fortune-1.8-2
> gcc-3.2-3
> gdbm-1.8.3-7
> ghostscript-7.05-2
> gnupg-1.2.2-1
> gperf-2.7.2-1
> grace-5.1.12-1
> grep-2.5-1
> groff-1.18.1-2
> gzip-1.3.3-4
> indent-2.2.8-1
> libbz2_0-1.0.2-1
> libdb3.1-3.1.17-2
> libdb3.1-devel-3.1.17-2
> libgdbm-1.8.0-5
> libgdbm3-1.8.3-3
> libguile12-1.6.0-1
> libguile12abi13-1.6.4-2
> libguile14-1.5.6-5
> libintl-0.10.38-3
> libintl1-0.10.40-1
> libkpathsea3abi13-2.0.2-2
> libncurses5-5.2-1
> libncurses6-5.2-8
> libpopt0-1.6.4-4
> libreadline4-4.1-2
> libtiff3-3.6.0-2
> libxml2-2.5.7-1
> libxslt-1.0.30-2
> links-0.96-1
> m4-1.4-1
> make-3.80-1
> man-1.5j-2
> mc-4.6.0-4
> more-2.11o-1
> nasm-0.98.37-1
> ncftp-3.1.4-1
> openssl096-0.9.6j-1
> patchutils-0.2.22-2
> perl-5.8.0-5
> postgresql-7.3.4-2
> psutils-1.17-1
> rsync-2.5.6-1
> texinfo-4.2-4
> textutils-2.0.21-1
> tidy-030201-1
> time-1.7-1
> units-1.77-1
> upx-1.24-1
> wget-1.8.2-2
> whois-4.6.2-1
>
> it would be very nice if the above packages were re-built against 1.5
If you remove all compatibility packages, and all programs which don't
handle uids/gids and don't need to handle multi-gigabyte files, there won't
be that many left. Of those that are, the *volunteer* maintainers will get
to them in time.
Max.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 19:25 ` Igor Pechtchanski
@ 2003-09-09 20:37 ` Sam Steingold
0 siblings, 0 replies; 12+ messages in thread
From: Sam Steingold @ 2003-09-09 20:37 UTC (permalink / raw)
To: cygwin
>* Igor Pechtchanski <crpugpun@pf.alh.rqh> [2003-09-09 15:25:51 -0400]:
>
> On Tue, 9 Sep 2003, Sam Steingold wrote:
>
> > shouldn't setup.exe refuse to install 1.5.3 unless all packages that
> > use 1.3 are also upgraded? like RPM and apt-get at al do?!
>
> I think you got it backwards. Cygwin 1.5 will run pre-1.5 programs
> with no problems. It's when you get a program compiled for 1.5 with
> an older DLL (e.g., 1.3.22) that you have a problem.
huh?! now I am thoroughly confused. thanks. :-)
I thought that binary (in)compatibility went both ways: if you build
against the old dll, you cannot run against the new one.
PS please do not CC me. I read all lists to which I post.
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
It's not just a language, it's an adventure. Common Lisp.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 19:49 ` Christopher Faylor
@ 2003-09-09 20:41 ` Sam Steingold
0 siblings, 0 replies; 12+ messages in thread
From: Sam Steingold @ 2003-09-09 20:41 UTC (permalink / raw)
To: cygwin
>* Christopher Faylor <pts-epz@pltjva.pbz> [2003-09-09 15:49:11 -0400]:
>
> On Tue, Sep 09, 2003 at 03:40:41PM -0400, Sam Steingold wrote:
> >I am getting spurious failures, and I would love to have them fixed.
>
> "spurious failures", eh? Yeah, we'll get right on that.
I am afraid I do not understand what you are saying
(English is not my native language).
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
Live free or die.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: package _version_ check
2003-09-09 19:40 ` Sam Steingold
2003-09-09 19:49 ` Christopher Faylor
2003-09-09 20:18 ` Max Bowsher
@ 2003-09-10 4:48 ` Charles Wilson
2 siblings, 0 replies; 12+ messages in thread
From: Charles Wilson @ 2003-09-10 4:48 UTC (permalink / raw)
To: cygwin
> gdbm-1.8.3-7
> libbz2_0-1.0.2-1
> libgdbm-1.8.0-5
> libgdbm3-1.8.3-3
> libintl-0.10.38-3
> libintl1-0.10.40-1
> libncurses5-5.2-1
> libncurses6-5.2-8
> libreadline4-4.1-2
> libtiff3-3.6.0-2
These are mine.
> it would be very nice if the above packages were re-built against 1.5
No, I don't think so. With one exception, those are ALL compatibility
packages. Even if they DID use the functions that were upgraded in
1.5.x, they STILL wouldn't be rebuilt. All new apps and libraries
should be linking against the current libs, which WERE rebuilt:
libbz2_1
libintl2
libncurses7
libreadline5
libtiff4
gdbm-1.8.3-7 **IS** the rebuilt package. It contains, however:
/usr/bin/dumpgdbm-1.3.22.exe
/usr/bin/loadgdbm-1.3.22.exe
which were compiled statically on a stock 1.3.22-only system. They are
used to -- yes, you guessed it -- provide backward compatibility and
migration support.
In the future, don't rely on a script to do your thinking for you.
Also, you might consider scanning the @#!#%!# cygwin-announce mailing
list archives. I didn't spend hours composing 30-odd detailed announce
messages -- ALL OF WHICH include 1.5.3-compatibility/requirement info --
for my health... Basically, any package which was announced in the
flurry after cygwin-1.5.3 was released was a 1.5.3 rebuild.
Further, cgf is correct: OLD programs will continue to run, without the
64bit functionality, seamlessly on a 1.5.3 system. Only the newly
recompiled apps, IF they access the new functions, won't be able to run
on a 1.3.22 system. But that's almost always true with any new release
of the kernel.
--
Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2003-09-10 4:48 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-09 18:22 package _version_ check Sam Steingold
2003-09-09 18:58 ` Max Bowsher
2003-09-09 19:40 ` Sam Steingold
2003-09-09 19:49 ` Christopher Faylor
2003-09-09 20:41 ` Sam Steingold
2003-09-09 20:18 ` Max Bowsher
2003-09-10 4:48 ` Charles Wilson
2003-09-09 19:02 ` Igor Pechtchanski
2003-09-09 19:14 ` Sam Steingold
2003-09-09 19:25 ` Igor Pechtchanski
2003-09-09 20:37 ` Sam Steingold
2003-09-09 20:00 ` Lapo Luchini
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).