[HEADSUP] Moving setup sources to git

[HEADSUP] Moving setup sources to git

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

Hi guys,

please don't check in anything to the setup CVS repo anymore.

I just created a git repo for setup:

  git clone cygwin.com:/git/cygwin-setup.git

The old CVS repo should be treated as R/O.

The new git repo should basically work now, but I'm not a git config
guru, so if stuff is missing, I appreciate configuration help!


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [HEADSUP] Moving setup sources to git

[Warren Young]

> On Feb 9, 2015, at 9:24 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> 
> I just created a git repo for setup:

About blinkin’ time.

But it should have been Fossil. ;)

Re: [HEADSUP] Moving setup sources to git

[Achim Gratz]

Corinna Vinschen writes:
> The new git repo should basically work now, but I'm not a git config
> guru, so if stuff is missing, I appreciate configuration help!

That's a relief!  I'll have to reconfigure my repo for setup to take
advantage of that fact before I can comment further.


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

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

Re: [HEADSUP] Moving setup sources to git

[Achim Gratz]

Corinna Vinschen writes:
> The new git repo should basically work now, but I'm not a git config
> guru, so if stuff is missing, I appreciate configuration help!

Looks good so far.  I assume that the SSH keys are already usable?


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

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [HEADSUP] Moving setup sources to git

[Frank Fesevur]

2015-02-09 17:24 GMT+01:00 Corinna Vinschen:
> please don't check in anything to the setup CVS repo anymore.
>
> I just created a git repo for setup:
>
>   git clone cygwin.com:/git/cygwin-setup.git

Just to let you know that the anonymous read-only access works:
git clone git://cygwin.com/git/cygwin-setup.git

But I tried to build setup and I have a problem with the dependencies.

README says I need various mingw libs. But if IIRC mingw is not
recommended anymore. I have installed mingw64 and the mingw64 variants
of those libs. But there is no mingw64 variant of liblzma. I've
installed all 5 packages containing "liblzma", but configure seems to
be unable to find it.

Do I still need the original mingw to compile setup or is the README outdated?

Regards,
Frank

Re: [HEADSUP] Moving setup sources to git

[Achim Gratz]

Frank Fesevur writes:
> README says I need various mingw libs. But if IIRC mingw is not
> recommended anymore. I have installed mingw64 and the mingw64 variants
> of those libs. But there is no mingw64 variant of liblzma. I've
> installed all 5 packages containing "liblzma", but configure seems to
> be unable to find it.
>
> Do I still need the original mingw to compile setup or is the README outdated?

I still carry the README patch below locally since it was not accepted
the last time around and it will likely need a few changes to be
up-to-date with today's reality.  For instance libgetopt++ is now
included in the tree, while I'd have preferred if it was a subtree or
submodule, which is more closely in line with the state it had in CVS.

--8<---------------cut here---------------start------------->8---
------------------------------------ README ------------------------------------
index b1586de..0499c6c 100644
@@ -3,33 +3,39 @@ for the Cygwin net releases.
 
 HOW TO BUILD:
 -------------
 Setup should build out-of-the-box on any Cygwin environment that has all the
 required packages installed:
-  - mingw-gcc-g++
   - make
-  - mingw-bzip2
-  - mingw-libgcrypt-devel
-  - mingw-liblzma-devel
-  - mingw-zlib
-  - and all packages that are dependencies of the above, i.e.  gcc-mingw-core,
-    mingw-runtime, binutils, w*api, etc.
+  - mingw64-gcc-g++
+  - mingw64-bzip2
+  - mingw64-libgcrypt
+  - mingw64-xz
+  - mingw64-zlib
+  - and all packages that are dependencies of the above
   - upx (optional)
 
 The following additional packages are required if building from CVS, not from
 a source tarball, or if you want to make changes to the build system.
   - recent autoconf
   - recent automake
   - recent libtool
   - flex
   - bison
 
+Additionally, libgetopt++ (also available from the cygwin-apps CVS at
+sourceware.org) must be available directly as a subdirectory
+libgetopt++ within the setup source directory.  It should be
+automatically populated by CVS, but if you are using tools like
+CVSgrab, you may need to fetch this yourself.
+
 Build commands:
 1) Configure using this option
    $ /path/to/setup/bootstrap.sh
-   This will automatically rebuild configure files and run configure in the
-   current directory.
+   This will automatically rebuild configure files and run configure
+   in the current directory.  The current directory must be outside
+   the source tree.
 2) $ make
 
 3) Wondering why your binary is so much bigger than the official releases?
    This removes debugging symbols:
    $ make strip
--8<---------------cut here---------------end--------------->8---


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

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [HEADSUP] Moving setup sources to git

[Frank Fesevur]

2015-02-09 20:46 GMT+01:00 Achim Gratz:
>  HOW TO BUILD:
>  -------------
>  Setup should build out-of-the-box on any Cygwin environment that has all the
>  required packages installed:
> -  - mingw-gcc-g++
>    - make
> -  - mingw-bzip2
> -  - mingw-libgcrypt-devel
> -  - mingw-liblzma-devel
> -  - mingw-zlib
> -  - and all packages that are dependencies of the above, i.e.  gcc-mingw-core,
> -    mingw-runtime, binutils, w*api, etc.
> +  - mingw64-gcc-g++
> +  - mingw64-bzip2
> +  - mingw64-libgcrypt
> +  - mingw64-xz
> +  - mingw64-zlib
> +  - and all packages that are dependencies of the above
>    - upx (optional)

Thanks, mingw64-xz did the trick.

Frank

Re: [HEADSUP] Moving setup sources to git

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

On Feb  9 20:46, Achim Gratz wrote:
> Frank Fesevur writes:
> > README says I need various mingw libs. But if IIRC mingw is not
> > recommended anymore. I have installed mingw64 and the mingw64 variants
> > of those libs. But there is no mingw64 variant of liblzma. I've
> > installed all 5 packages containing "liblzma", but configure seems to
> > be unable to find it.
> >
> > Do I still need the original mingw to compile setup or is the README outdated?
> 
> I still carry the README patch below locally since it was not accepted

Please apply.  That should work, given the file perms on sware...


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [HEADSUP] Moving setup sources to git

[Jon TURNEY]

On 09/02/2015 19:46, Achim Gratz wrote:
> Frank Fesevur writes:
>> README says I need various mingw libs. But if IIRC mingw is not
>> recommended anymore. I have installed mingw64 and the mingw64 variants
>> of those libs. But there is no mingw64 variant of liblzma. I've
>> installed all 5 packages containing "liblzma", but configure seems to
>> be unable to find it.
>>
>> Do I still need the original mingw to compile setup or is the README outdated?
>
> I still carry the README patch below locally since it was not accepted
> the last time around and it will likely need a few changes to be
> up-to-date with today's reality.  For instance libgetopt++ is now
> included in the tree, while I'd have preferred if it was a subtree or
> submodule, which is more closely in line with the state it had in CVS.
>
> --8<---------------cut here---------------start------------->8---
> ------------------------------------ README ------------------------------------
> index b1586de..0499c6c 100644
> @@ -3,33 +3,39 @@ for the Cygwin net releases.
>
>   HOW TO BUILD:
>   -------------
>   Setup should build out-of-the-box on any Cygwin environment that has all the
>   required packages installed:
> -  - mingw-gcc-g++
>     - make
> -  - mingw-bzip2
> -  - mingw-libgcrypt-devel
> -  - mingw-liblzma-devel
> -  - mingw-zlib
> -  - and all packages that are dependencies of the above, i.e.  gcc-mingw-core,
> -    mingw-runtime, binutils, w*api, etc.
> +  - mingw64-gcc-g++
> +  - mingw64-bzip2
> +  - mingw64-libgcrypt
> +  - mingw64-xz
> +  - mingw64-zlib
> +  - and all packages that are dependencies of the above

I'm not sure these are actually package names since they are missing the 
arch?

>     - upx (optional)
>
>   The following additional packages are required if building from CVS, not from
>   a source tarball, or if you want to make changes to the build system.
>     - recent autoconf
>     - recent automake
>     - recent libtool
>     - flex
>     - bison
>
> +Additionally, libgetopt++ (also available from the cygwin-apps CVS at
> +sourceware.org) must be available directly as a subdirectory
> +libgetopt++ within the setup source directory.  It should be
> +automatically populated by CVS, but if you are using tools like
> +CVSgrab, you may need to fetch this yourself.
> +

This doesn't make sense anymore.

>   Build commands:
>   1) Configure using this option
>      $ /path/to/setup/bootstrap.sh
> -   This will automatically rebuild configure files and run configure in the
> -   current directory.
> +   This will automatically rebuild configure files and run configure
> +   in the current directory.  The current directory must be outside
> +   the source tree.

This isn't true.

Re: [HEADSUP] Moving setup sources to git

[Achim Gratz]

Jon TURNEY writes:
> I'm not sure these are actually package names since they are missing
> the arch?

They were, at the time I created that patch.

>> +Additionally, libgetopt++ (also available from the cygwin-apps CVS at
>> +sourceware.org) must be available directly as a subdirectory
>> +libgetopt++ within the setup source directory.  It should be
>> +automatically populated by CVS, but if you are using tools like
>> +CVSgrab, you may need to fetch this yourself.
>> +
>
> This doesn't make sense anymore.

Right, although I still think libgetopt++ should be a subtree or
submodule and not integrated into cygwin-setup.

>>   Build commands:
>>   1) Configure using this option
>>      $ /path/to/setup/bootstrap.sh
>> -   This will automatically rebuild configure files and run configure in the
>> -   current directory.
>> +   This will automatically rebuild configure files and run configure
>> +   in the current directory.  The current directory must be outside
>> +   the source tree.
>
> This isn't true.

At the time of writing an in-tree build configuration did not work for
me, although that later turned out to be an unrelated problem IIRC.  At
the moment I actually build in-tree since you can't configure both
architectures in an out-of-tree build anyway.  If I have lots of time
unexpectedly I might try to figure out how to move the autoconf
machinery out of the source tree to make it possible to build both
architectures from a single worktree.


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

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Re: [HEADSUP] Moving setup sources to git

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]

On Feb  9 22:48, Achim Gratz wrote:
> At the time of writing an in-tree build configuration did not work for
> me, although that later turned out to be an unrelated problem IIRC.  At
> the moment I actually build in-tree since you can't configure both
> architectures in an out-of-tree build anyway.

This.  I don't understand.  Here's what I do:

  $ mkdir -p ~/src/setup
  $ cd !$
  $ cvs -d :ext:corinna@sourceware.org:/cvs/cygwin-apps ^C
  <swear at old habits>
  $ git clone cygwin.com:/git/cygwin-setup.git setup
  [...bla...]
  $ cd setup
  $ bash -c "NOCONFIGURE=1 ./bootstrap.sh"
  $ cd ..
  $ mkdir i686 x86_64
  $ cat > conf.sh <<EOF
  #!/bin/bash
  cpu=$(basename $PWD)
  [ -n "$cpu" ] && \
    ../setup/configure --host=$cpu-w64-mingw32 --target=$cpu-w64-mingw32
  EOF
  $ chmod +x conf.sh
  $ cd i686
  $ ../conf.sh
  [...more bla...]
  $ make -j12 upx
  [...even more bla...]
  $ cd ../x86_64
  $ ../conf.sh
  [...lots of bla...]
  $ make -j12 upx
  [...excessive bla...]

Now I have the 32 bit version in ~/src/setup/i686 and the 64 bit version
in ~/src/setup/x86_64.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [HEADSUP] Moving setup sources to git

[Vin Shelton]

I thought I would give this a go, to see how the documentation works
for me, but no joy:

On Tue, Feb 10, 2015 at 3:31 AM, Corinna Vinschen wrote:
> git clone cygwin.com:/git/cygwin-setup.git setup

git clone cygwin.com:/git/cygwin-setup.git
Cloning into 'cygwin-setup'...
Permission denied.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Regards,
  Vin Shelton

Re: [HEADSUP] Moving setup sources to git

[Frank Fesevur]

2015-02-10 14:55 GMT+01:00 Vin Shelton:
> git clone cygwin.com:/git/cygwin-setup.git
> Cloning into 'cygwin-setup'...
> Permission denied.
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.

I assume that you (just like me) didn't have write access to the
original CVS repo.

This worked for me:
git clone git://cygwin.com/git/cygwin-setup.git

Regards,
Frank

Re: [HEADSUP] Moving setup sources to git

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Feb 10 15:13, Frank Fesevur wrote:
> 2015-02-10 14:55 GMT+01:00 Vin Shelton:
> > git clone cygwin.com:/git/cygwin-setup.git
> > Cloning into 'cygwin-setup'...
> > Permission denied.
> > fatal: Could not read from remote repository.
> >
> > Please make sure you have the correct access rights
> > and the repository exists.
> 
> I assume that you (just like me) didn't have write access to the
> original CVS repo.
> 
> This worked for me:
> git clone git://cygwin.com/git/cygwin-setup.git

Thanks guys.  I fixed the documentation on
https://sourceware.org/cygwin-apps/setup.html


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [HEADSUP] Moving setup sources to git

[Achim Gratz]

Corinna Vinschen writes:
> On Feb  9 22:48, Achim Gratz wrote:
>> At the time of writing an in-tree build configuration did not work for
>> me, although that later turned out to be an unrelated problem IIRC.  At
>> the moment I actually build in-tree since you can't configure both
>> architectures in an out-of-tree build anyway.
>
> This.  I don't understand.  Here's what I do:

Thanks.  I don't understand it either anymore because I just tried this
again (in a slightly different way because I build for 32bit on 32bit
and 64bit on 64bit) and it now works.  I'm not sure what went wrong the
first time I tried it, but it was telling me something about me needing
to reconfigure and throwing away the cache each time I built for the
other architecture.

>   $ bash -c "NOCONFIGURE=1 ./bootstrap.sh"

Very obvious now... but still too well hidden.

>   $ cat > conf.sh <<EOF
>   #!/bin/bash
>   cpu=$(basename $PWD)
>   [ -n "$cpu" ] && \
>     ../setup/configure --host=$cpu-w64-mingw32 --target=$cpu-w64-mingw32
>   EOF

That's been bothering me for a while, the test for determining the build
and host type in bootstrap.sh just doesn't give the right results most
of the time and I always have to add the --host=<...> manually.  What (if
anything) is --target=<..> doing?


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

Re: [HEADSUP] Moving setup sources to git

[David Stacey]

On 09/02/15 16:24, Corinna Vinschen wrote:
> I just created a git repo for setup:
>
>    git clone cygwin.com:/git/cygwin-setup.git

For the last ten months, I've been running the Coverity Scan static 
analyser over Cygwin snapshots. Do you want me to continue using the 
snapshots, or would you prefer me to switch to git master? Would there 
be much difference between the two?

Dave.

Re: [HEADSUP] Moving setup sources to git

[Achim Gratz]

David Stacey writes:
> For the last ten months, I've been running the Coverity Scan static
> analyser over Cygwin snapshots. Do you want me to continue using the
> snapshots, or would you prefer me to switch to git master? Would there
> be much difference between the two?

I think just cygwin setup has been converted to Git… see
https://sourceware.org/git/

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

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

Re: [HEADSUP] Moving setup sources to git

[David Stacey]

On 10/02/15 18:53, Achim Gratz wrote:
> David Stacey writes:
>> For the last ten months, I've been running the Coverity Scan static
>> analyser over Cygwin snapshots. Do you want me to continue using the
>> snapshots, or would you prefer me to switch to git master? Would there
>> be much difference between the two?
> I think just cygwin setup has been converted to Git… see
> https://sourceware.org/git/

OK, sorry. My confusion.

Dave.

Re: [HEADSUP] Moving setup sources to git

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

On Feb 10 18:56, David Stacey wrote:
> On 10/02/15 18:53, Achim Gratz wrote:
> >David Stacey writes:
> >>For the last ten months, I've been running the Coverity Scan static
> >>analyser over Cygwin snapshots. Do you want me to continue using the
> >>snapshots, or would you prefer me to switch to git master? Would there
> >>be much difference between the two?
> >I think just cygwin setup has been converted to Git… see
> >https://sourceware.org/git/
> 
> OK, sorry. My confusion.

Apart from that, we're going to swithc Cygwin to git as well in the next
couple of ... days or weeks, I'm not sure yet.

Anyway, as soon as we switched, use whatever you prefer.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [HEADSUP] Moving setup sources to git

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]

On Feb 10 18:01, Achim Gratz wrote:
> Corinna Vinschen writes:
> > On Feb  9 22:48, Achim Gratz wrote:
> >> At the time of writing an in-tree build configuration did not work for
> >> me, although that later turned out to be an unrelated problem IIRC.  At
> >> the moment I actually build in-tree since you can't configure both
> >> architectures in an out-of-tree build anyway.
> >
> > This.  I don't understand.  Here's what I do:
> 
> Thanks.  I don't understand it either anymore because I just tried this
> again (in a slightly different way because I build for 32bit on 32bit
> and 64bit on 64bit) and it now works.  I'm not sure what went wrong the
> first time I tried it, but it was telling me something about me needing
> to reconfigure and throwing away the cache each time I built for the
> other architecture.
> 
> >   $ bash -c "NOCONFIGURE=1 ./bootstrap.sh"
> 
> Very obvious now... but still too well hidden.
> 
> >   $ cat > conf.sh <<EOF
> >   #!/bin/bash
> >   cpu=$(basename $PWD)
> >   [ -n "$cpu" ] && \
> >     ../setup/configure --host=$cpu-w64-mingw32 --target=$cpu-w64-mingw32
> >   EOF
> 
> That's been bothering me for a while, the test for determining the build
> and host type in bootstrap.sh just doesn't give the right results most
> of the time and I always have to add the --host=<...> manually.  What (if
> anything) is --target=<..> doing?

Some autoconf thingy.  I'm not sure anymore but it could have had to do
with cross building on Linux.  After I created the conf.sh files I'm
working with them and never looked again.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [HEADSUP] Moving setup sources to git

[Achim Gratz]

Corinna Vinschen writes:
>> I still carry the README patch below locally since it was not accepted
>
> Please apply.  That should work, given the file perms on sware...

Done, with the changes that have accumulated since the original patch.


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