64 bit HEADSUP: Restart of *everything* today

[Corinna Vinschen]

Hi guys,


good news: Kai finished his first cut (pre-cleanup, pre-code comments)
version of his medium/large code model patch. I already generated a
complete new toolchain and it looks pretty good. The default code model
for Cygwin applications is "medium". This means, external code is
referenced as usual, external data is referenced via a (pseudo-)GOT
table similar to ELF files.
This raises the code size marginally (about 3 to 5%), but it allows to
access external variables in the entire 64 bit address range without the
requirement to declare these symbols as dllimport symbols.

While I was at it, I changed Cygwin so that "environ" is now a simple
external variable. The 32 bit code is rather convoluted, probably
because the original implementers couldn't export simple variables
way back when.

You're asking for the dowside? Here's the downside:

Our entire micro distro in ftp://cygwin.com/pub/cygwin/64bit/install
is for the birds. Almost no application will run anymore, unless it
gets rebuilt from scratch with the new toolchain.

Therefore I moved everything to ftp://cygwin.com/pub/cygwin/64bit/OLD
for now. I will upload new toolchains, dash, tcsh, coreutils etc. during
this week, parts of it already today, so we can build more packages
from scratch ASAP.

Ok, that's all folks,
Corinna

[Corinna Vinschen]

Post by Corinna Vinschen
Hi guys,
good news: Kai finished his first cut (pre-cleanup, pre-code comments)
version of his medium/large code model patch. I already generated a
complete new toolchain and it looks pretty good. The default code model
for Cygwin applications is "medium". This means, external code is
referenced as usual, external data is referenced via a (pseudo-)GOT
table similar to ELF files.
This raises the code size marginally (about 3 to 5%), but it allows to
access external variables in the entire 64 bit address range without the
requirement to declare these symbols as dllimport symbols.
While I was at it, I changed Cygwin so that "environ" is now a simple
external variable. The 32 bit code is rather convoluted, probably
because the original implementers couldn't export simple variables
way back when.
Our entire micro distro in ftp://cygwin.com/pub/cygwin/64bit/install
is for the birds. Almost no application will run anymore, unless it
gets rebuilt from scratch with the new toolchain.
Therefore I moved everything to ftp://cygwin.com/pub/cygwin/64bit/OLD
for now. I will upload new toolchains, dash, tcsh, coreutils etc. during
this week, parts of it already today, so we can build more packages
from scratch ASAP.
Ok, that's all folks,

Uh, not quite. More on the good news front: BFD, binutils and GDB
patches have gone upstream today. Only the GCC patches are missing yet,
because we have to wait until new functionality is accepted into the GCC
tree (stage 1). That's supposed to be end of this month.


Corinna

[Corinna Vinschen]

Post by Corinna Vinschen
Our entire micro distro in ftp://cygwin.com/pub/cygwin/64bit/install
is for the birds. Almost no application will run anymore, unless it
gets rebuilt from scratch with the new toolchain.
Therefore I moved everything to ftp://cygwin.com/pub/cygwin/64bit/OLD
for now. I will upload new toolchains, dash, tcsh, coreutils etc. during
this week, parts of it already today, so we can build more packages
from scratch ASAP.

Ok, I think I have now uploaded everything we need for a start.

In ftp://cygwin.com/pub/cygwin/64bit/ you'll find

binary-toolchain-x86_64-pc-linux-x-x86_64-pc-cygwin-20130305.tar.xz
bootstrap.sh
x86_64-pc-cygwin-gcc-20130305.patch

Since binutils and gdb patches are upstream, no patch file for them.

In ftp://cygwin.com/pub/cygwin/64bit/install/ you'll find

base-cygwin-toolchain-install-first-20130305-2.x86_64.tar.xz
coreutils-8.15-1.x86_64.tar.xz
dash-0.5.7-2.x86_64.tar.xz
diffutils-3.2-2.x86_64.tar.xz
expat-2.1.0-2.x86_64.tar.xz
file-5.11-2.x86_64.tar.xz
findutils-4.5.9-3.x86_64.tar.xz
gawk-4.0.2-3.x86_64.tar.xz
gdb-7.5.50.20130305-cvs-2.x86_64.tar.xz
grep-2.6.3-3.x86_64.tar.xz
m4-1.4.16-2.x86_64.tar.xz
make-3.82-2.x86_64.tar.xz
md5.sum
rebase-4.4.0-2.x86_64.tar.xz
sed-4.2.1-2.x86_64.tar.xz
tar-1.26-2.x86_64.tar.xz
tcsh-6.18.01-2.x86_64.tar.xz
termcap-1.3.1-1.x86_64.xz

When you untar from 32 bit Cygwin, keep in mind to untar the archives
with the -k option so that the usr/bin and usr/lib symlinks from the
base archive are not overwritten!


Have fun,
Corinna

[Corinna Vinschen]

Post by Corinna Vinschen

Post by Corinna Vinschen
Our entire micro distro in ftp://cygwin.com/pub/cygwin/64bit/install
is for the birds. Almost no application will run anymore, unless it
gets rebuilt from scratch with the new toolchain.
Therefore I moved everything to ftp://cygwin.com/pub/cygwin/64bit/OLD
for now. I will upload new toolchains, dash, tcsh, coreutils etc. during
this week, parts of it already today, so we can build more packages
from scratch ASAP.

Ok, I think I have now uploaded everything we need for a start.
In ftp://cygwin.com/pub/cygwin/64bit/ you'll find
binary-toolchain-x86_64-pc-linux-x-x86_64-pc-cygwin-20130305.tar.xz
bootstrap.sh
x86_64-pc-cygwin-gcc-20130305.patch
Since binutils and gdb patches are upstream, no patch file for them.
In ftp://cygwin.com/pub/cygwin/64bit/install/ you'll find
base-cygwin-toolchain-install-first-20130305-2.x86_64.tar.xz
coreutils-8.15-1.x86_64.tar.xz
dash-0.5.7-2.x86_64.tar.xz
diffutils-3.2-2.x86_64.tar.xz
expat-2.1.0-2.x86_64.tar.xz
file-5.11-2.x86_64.tar.xz
findutils-4.5.9-3.x86_64.tar.xz
gawk-4.0.2-3.x86_64.tar.xz
gdb-7.5.50.20130305-cvs-2.x86_64.tar.xz
grep-2.6.3-3.x86_64.tar.xz
m4-1.4.16-2.x86_64.tar.xz
make-3.82-2.x86_64.tar.xz
md5.sum
rebase-4.4.0-2.x86_64.tar.xz
sed-4.2.1-2.x86_64.tar.xz
tar-1.26-2.x86_64.tar.xz
tcsh-6.18.01-2.x86_64.tar.xz
termcap-1.3.1-1.x86_64.xz

I just added

cygrunsrv-1.41-1.x86_64.tar.xz


Corinna

[Corinna Vinschen]

Post by Corinna Vinschen

Post by Corinna Vinschen

Post by Corinna Vinschen
Our entire micro distro in ftp://cygwin.com/pub/cygwin/64bit/install
is for the birds. Almost no application will run anymore, unless it
gets rebuilt from scratch with the new toolchain.
Therefore I moved everything to ftp://cygwin.com/pub/cygwin/64bit/OLD
for now. I will upload new toolchains, dash, tcsh, coreutils etc. during
this week, parts of it already today, so we can build more packages
from scratch ASAP.

Ok, I think I have now uploaded everything we need for a start.
In ftp://cygwin.com/pub/cygwin/64bit/ you'll find
binary-toolchain-x86_64-pc-linux-x-x86_64-pc-cygwin-20130305.tar.xz
bootstrap.sh
x86_64-pc-cygwin-gcc-20130305.patch
Since binutils and gdb patches are upstream, no patch file for them.
In ftp://cygwin.com/pub/cygwin/64bit/install/ you'll find
base-cygwin-toolchain-install-first-20130305-2.x86_64.tar.xz
coreutils-8.15-1.x86_64.tar.xz
dash-0.5.7-2.x86_64.tar.xz
diffutils-3.2-2.x86_64.tar.xz
expat-2.1.0-2.x86_64.tar.xz
file-5.11-2.x86_64.tar.xz
findutils-4.5.9-3.x86_64.tar.xz
gawk-4.0.2-3.x86_64.tar.xz
gdb-7.5.50.20130305-cvs-2.x86_64.tar.xz
grep-2.6.3-3.x86_64.tar.xz
m4-1.4.16-2.x86_64.tar.xz
make-3.82-2.x86_64.tar.xz
md5.sum
rebase-4.4.0-2.x86_64.tar.xz
sed-4.2.1-2.x86_64.tar.xz
tar-1.26-2.x86_64.tar.xz
tcsh-6.18.01-2.x86_64.tar.xz
termcap-1.3.1-1.x86_64.xz

I just added
cygrunsrv-1.41-1.x86_64.tar.xz

as well as

patch-2.6.1-1.x86_64.tar.xz
shutdown-1.8-1.x86_64.tar.xz


Corinna

[Corinna Vinschen]

Post by Corinna Vinschen

Post by Corinna Vinschen

Post by Corinna Vinschen
Ok, I think I have now uploaded everything we need for a start.
In ftp://cygwin.com/pub/cygwin/64bit/ you'll find
binary-toolchain-x86_64-pc-linux-x-x86_64-pc-cygwin-20130305.tar.xz
bootstrap.sh
x86_64-pc-cygwin-gcc-20130305.patch
Since binutils and gdb patches are upstream, no patch file for them.
In ftp://cygwin.com/pub/cygwin/64bit/install/ you'll find
base-cygwin-toolchain-install-first-20130305-2.x86_64.tar.xz
coreutils-8.15-1.x86_64.tar.xz
dash-0.5.7-2.x86_64.tar.xz
diffutils-3.2-2.x86_64.tar.xz
expat-2.1.0-2.x86_64.tar.xz
file-5.11-2.x86_64.tar.xz
findutils-4.5.9-3.x86_64.tar.xz
gawk-4.0.2-3.x86_64.tar.xz
gdb-7.5.50.20130305-cvs-2.x86_64.tar.xz
grep-2.6.3-3.x86_64.tar.xz
m4-1.4.16-2.x86_64.tar.xz
make-3.82-2.x86_64.tar.xz
md5.sum
rebase-4.4.0-2.x86_64.tar.xz
sed-4.2.1-2.x86_64.tar.xz
tar-1.26-2.x86_64.tar.xz
tcsh-6.18.01-2.x86_64.tar.xz
termcap-1.3.1-1.x86_64.xz

I just added
cygrunsrv-1.41-1.x86_64.tar.xz

as well as
patch-2.6.1-1.x86_64.tar.xz
shutdown-1.8-1.x86_64.tar.xz

as well as

cpio-2.11-1.x86_64.tar.xz
ipc-utils-1.0-1.x86_64.tar.xz
mt-2.3.3-1.x86_64.tar.xz
nc-1.107-1.x86_64.tar.xz
nc6-1.0-1.x86_64.tar.xz

<blatant hint>
What I'm missing most at this point in time are mintty and vim
packages. And bash users will miss bash...
</blatant hint>


Corinna

[Corinna Vinschen]

Post by Corinna Vinschen

Post by Corinna Vinschen

Post by Corinna Vinschen

Post by Corinna Vinschen
Ok, I think I have now uploaded everything we need for a start.
In ftp://cygwin.com/pub/cygwin/64bit/ you'll find
binary-toolchain-x86_64-pc-linux-x-x86_64-pc-cygwin-20130305.tar.xz
bootstrap.sh
x86_64-pc-cygwin-gcc-20130305.patch
Since binutils and gdb patches are upstream, no patch file for them.
In ftp://cygwin.com/pub/cygwin/64bit/install/ you'll find
base-cygwin-toolchain-install-first-20130305-2.x86_64.tar.xz
coreutils-8.15-1.x86_64.tar.xz
dash-0.5.7-2.x86_64.tar.xz
diffutils-3.2-2.x86_64.tar.xz
expat-2.1.0-2.x86_64.tar.xz
file-5.11-2.x86_64.tar.xz
findutils-4.5.9-3.x86_64.tar.xz
gawk-4.0.2-3.x86_64.tar.xz
gdb-7.5.50.20130305-cvs-2.x86_64.tar.xz
grep-2.6.3-3.x86_64.tar.xz
m4-1.4.16-2.x86_64.tar.xz
make-3.82-2.x86_64.tar.xz
md5.sum
rebase-4.4.0-2.x86_64.tar.xz
sed-4.2.1-2.x86_64.tar.xz
tar-1.26-2.x86_64.tar.xz
tcsh-6.18.01-2.x86_64.tar.xz
termcap-1.3.1-1.x86_64.xz

I just added
cygrunsrv-1.41-1.x86_64.tar.xz

as well as
patch-2.6.1-1.x86_64.tar.xz
shutdown-1.8-1.x86_64.tar.xz

as well as
cpio-2.11-1.x86_64.tar.xz
ipc-utils-1.0-1.x86_64.tar.xz
mt-2.3.3-1.x86_64.tar.xz
nc-1.107-1.x86_64.tar.xz
nc6-1.0-1.x86_64.tar.xz

as well as

bison-2.7-1.x86_64.tar.xz
flex-2.5.35-1.x86_64.tar.xz

Post by Corinna Vinschen
<blatant hint>
What I'm missing most at this point in time are mintty and vim
packages. And bash users will miss bash...
</blatant hint>

Corinna

[Corinna Vinschen]

Post by Corinna Vinschen
Ok, I think I have now uploaded everything we need for a start.
[...]

I just uploaded

catgets-1.1-2-src.tar.bz2
catgets-1.1-2.tar.bz2
libcatgets-devel-1.1-2.tar.bz2
libcatgets1-1.1-2.tar.bz2

These are my first cygport-created packages, using basically my 32 bit
cygport file, so they are bz2 and missing the x86_64 in the name.


Corinna

[Corinna Vinschen]

Post by Corinna Vinschen

Post by Corinna Vinschen
Ok, I think I have now uploaded everything we need for a start.
[...]

I just uploaded
catgets-1.1-2-src.tar.bz2
catgets-1.1-2.tar.bz2
libcatgets-devel-1.1-2.tar.bz2
libcatgets1-1.1-2.tar.bz2
These are my first cygport-created packages, using basically my 32 bit
cygport file, so they are bz2 and missing the x86_64 in the name.

Which leads to a question: When do we go entirely "distro"-style?
It's nice to have a lot of packages to play and build more packages,
but it's pretty obvious double (or triple) work.

We don't have enough packages yet to make a 64 bit distro work with
setup (mostely bash is missing), but I guess we can seriously consider
that not too far in the future. A week? Two?

And how do we start? Would it make sense to create a new subdir
64bit/release already today and fill it step by step with packages
which can be considered finished and all dependencies resolved?

The 64bit/release dir could then simply be moved to it's ultimate
position as soon as we go public.


Corinna

[Yaakov (Cygwin/X)]

Post by Corinna Vinschen
Which leads to a question: When do we go entirely "distro"-style?
It's nice to have a lot of packages to play and build more packages,
but it's pretty obvious double (or triple) work.
We don't have enough packages yet to make a 64 bit distro work with
setup (mostely bash is missing), but I guess we can seriously consider
that not too far in the future. A week? Two?

Yeah, if not sooner. As I'm building everything with cygport, it's a
lot easier for me to upload a tree than these single ad-hoc packages.

Post by Corinna Vinschen
And how do we start? Would it make sense to create a new subdir
64bit/release already today and fill it step by step with packages
which can be considered finished and all dependencies resolved?
The 64bit/release dir could then simply be moved to it's ultimate
position as soon as we go public.

Sounds good to me.


Yaakov

[Corinna Vinschen]

Post by Yaakov (Cygwin/X)

Post by Corinna Vinschen
Which leads to a question: When do we go entirely "distro"-style?
It's nice to have a lot of packages to play and build more packages,
but it's pretty obvious double (or triple) work.
We don't have enough packages yet to make a 64 bit distro work with
setup (mostely bash is missing), but I guess we can seriously consider
that not too far in the future. A week? Two?

Yeah, if not sooner. As I'm building everything with cygport, it's a
lot easier for me to upload a tree than these single ad-hoc packages.

Post by Corinna Vinschen
And how do we start? Would it make sense to create a new subdir
64bit/release already today and fill it step by step with packages
which can be considered finished and all dependencies resolved?
The 64bit/release dir could then simply be moved to it's ultimate
position as soon as we go public.

Sounds good to me.

Ok, I created that 64bit/release dir, which is just a bit lonely right
now. I also pulled my catgets packages again, since they were broken.


Corinna

[Corinna Vinschen]

Post by Corinna Vinschen

Post by Yaakov (Cygwin/X)

Post by Corinna Vinschen
Which leads to a question: When do we go entirely "distro"-style?
It's nice to have a lot of packages to play and build more packages,
but it's pretty obvious double (or triple) work.
We don't have enough packages yet to make a 64 bit distro work with
setup (mostely bash is missing), but I guess we can seriously consider
that not too far in the future. A week? Two?

Yeah, if not sooner. As I'm building everything with cygport, it's a
lot easier for me to upload a tree than these single ad-hoc packages.

Post by Corinna Vinschen
And how do we start? Would it make sense to create a new subdir
64bit/release already today and fill it step by step with packages
which can be considered finished and all dependencies resolved?
The 64bit/release dir could then simply be moved to it's ultimate
position as soon as we go public.

Sounds good to me.

Ok, I created that 64bit/release dir, which is just a bit lonely right
now. I also pulled my catgets packages again, since they were broken.

I re-uploaded the catgets packages and added them to the new, shiny,
very empty release subdir (yay!)


Corinna

[Teemu Nätkinniemi]

Here's Bash 4.1.10

http://sourceforge.net/projects/cyg64files/files/bash-4.1.10.x86_64.tar.bz2

[Peter Rosin]

Post by Teemu Nätkinniemi
Here's Bash 4.1.10
http://sourceforge.net/projects/cyg64files/files/bash-4.1.10.x86_64.tar.bz2

$ bash
/usr/bin/bash.exe: error while loading shared libraries: cygreadline7.dll: cannot open shared object file: No such file or directory

Cheers,
Peter

[Teemu Nätkinniemi]

Post by Peter Rosin

Post by Teemu Nätkinniemi
Here's Bash 4.1.10
http://sourceforge.net/projects/cyg64files/files/bash-4.1.10.x86_64.tar.bz2

$ bash
/usr/bin/bash.exe: error while loading shared libraries: cygreadline7.dll: cannot open shared object file: No such file or directory

You can get dependencies from the ftp:

ftp://ftp.cygwin.com/pub/cygwin/64bit/release/

[Peter Rosin]

Post by Teemu Nätkinniemi

Post by Peter Rosin

Post by Teemu Nätkinniemi
Here's Bash 4.1.10
http://sourceforge.net/projects/cyg64files/files/bash-4.1.10.x86_64.tar.bz2

$ bash
/usr/bin/bash.exe: error while loading shared libraries: cygreadline7.dll: cannot open shared object file: No such file or directory

ftp://ftp.cygwin.com/pub/cygwin/64bit/release/

Face-palm. Sorry for the noise.

Cheers,
Peter

[Teemu Nätkinniemi]

I added working *shared* Perl 5.16.2. Recent improvements to Cygwin64
made this version possible. I also added Autoconf 2.69 and Automake
1.13.1 and removed the old versions.

https://sourceforge.net/projects/cyg64files/files/automake-1.13.1-1.x86_64.tar.xz/download

https://sourceforge.net/projects/cyg64files/files/autoconf-2.69-3.x86_64.tar.xz/download

https://sourceforge.net/projects/cyg64files/files/perl-5.16.2-3.x86_64.tar.xz/download

https://sourceforge.net/projects/cyg64files/files/?

[Reini Urban]

I added working *shared* Perl 5.16.2. Recent improvements to Cygwin64 made
this version possible. I also added Autoconf 2.69 and Automake 1.13.1 and
removed the old versions.
https://sourceforge.net/projects/cyg64files/files/perl-5.16.2-3.x86_64.tar.xz/download

Hi Teemu,

Great.
But I'm, not quite happy with 5.16 being released on cygwin. First
there is a new 5.14.4
and 5.16.3 which do fix most security issues, but secondly 5.16 itself
is so inherently
insecure, that I warned packagers not to distribute it at all. And did
choose to not
fully disclosure the issues publicly since it affects a lot of people.

It's not that cygwin is such a secure platform that it makes a
difference, but still, as I
as maintainer am the one who found all those bugs and p5p is still in
denial of the more
important issues (they fixed some minor ones, apperently just to avoid
trouble), it would
be nice to release 5.14.4 instead. 5.14.4 can be highly recommended.

PS: The author of the problems confirmed my issues with 5.16, and there slowly
coming some momentum to fix it for 5.18.

[Teemu Nätkinniemi]

Post by Reini Urban

I added working *shared* Perl 5.16.2. Recent improvements to Cygwin64 made
this version possible. I also added Autoconf 2.69 and Automake 1.13.1 and
removed the old versions.
https://sourceforge.net/projects/cyg64files/files/perl-5.16.2-3.x86_64.tar.xz/download

Hi Teemu,
Great.
But I'm, not quite happy with 5.16 being released on cygwin. First
there is a new 5.14.4
and 5.16.3 which do fix most security issues, but secondly 5.16 itself
is so inherently
insecure, that I warned packagers not to distribute it at all. And did
choose to not
fully disclosure the issues publicly since it affects a lot of people.

I wasn't aware of any security issues and basically just wanted to
release the latest version of Perl to get autotools working. I can
compile a new version tomorrow (5.14.4).

[Teemu Nätkinniemi]

Post by Reini Urban
trouble), it would
be nice to release 5.14.4 instead. 5.14.4 can be highly recommended.

I compiled 5.14.4-RC2 and uploaded it to sf.

http://sourceforge.net/projects/cyg64files/files/perl-5.14.4-1.x86_64.tar.xz/download

I tried using the script that is used to build official Cygwin releases
but that seems to have a lot of problems with permissions when packaging
so I am not sure if the archive is actually complete or not. I've
uploaded it to:

https://sourceforge.net/projects/cyg64files/files/Perl-testing/

[Andy Koppe]

Post by Corinna Vinschen

Post by Corinna Vinschen

Post by Corinna Vinschen

Post by Corinna Vinschen
Ok, I think I have now uploaded everything we need for a start.
In ftp://cygwin.com/pub/cygwin/64bit/ you'll find
binary-toolchain-x86_64-pc-linux-x-x86_64-pc-cygwin-20130305.tar.xz
bootstrap.sh
x86_64-pc-cygwin-gcc-20130305.patch
Since binutils and gdb patches are upstream, no patch file for them.
In ftp://cygwin.com/pub/cygwin/64bit/install/ you'll find
base-cygwin-toolchain-install-first-20130305-2.x86_64.tar.xz
coreutils-8.15-1.x86_64.tar.xz
dash-0.5.7-2.x86_64.tar.xz
diffutils-3.2-2.x86_64.tar.xz
expat-2.1.0-2.x86_64.tar.xz
file-5.11-2.x86_64.tar.xz
findutils-4.5.9-3.x86_64.tar.xz
gawk-4.0.2-3.x86_64.tar.xz
gdb-7.5.50.20130305-cvs-2.x86_64.tar.xz
grep-2.6.3-3.x86_64.tar.xz
m4-1.4.16-2.x86_64.tar.xz
make-3.82-2.x86_64.tar.xz
md5.sum
rebase-4.4.0-2.x86_64.tar.xz
sed-4.2.1-2.x86_64.tar.xz
tar-1.26-2.x86_64.tar.xz
tcsh-6.18.01-2.x86_64.tar.xz
termcap-1.3.1-1.x86_64.xz

I just added
cygrunsrv-1.41-1.x86_64.tar.xz

as well as
patch-2.6.1-1.x86_64.tar.xz
shutdown-1.8-1.x86_64.tar.xz

as well as
cpio-2.11-1.x86_64.tar.xz
ipc-utils-1.0-1.x86_64.tar.xz
mt-2.3.3-1.x86_64.tar.xz
nc-1.107-1.x86_64.tar.xz
nc6-1.0-1.x86_64.tar.xz
<blatant hint>
What I'm missing most at this point in time are mintty and vim
packages. And bash users will miss bash...
</blatant hint>

Mintty's been added now.

Andy