Re: Building setup.exe: conflicting declarations of ssize_t

2011-09-09 Thread Christopher Faylor
On Wed, Sep 07, 2011 at 08:18:30AM -0400, Ken Brown wrote:
>On 9/6/2011 9:52 PM, Christopher Faylor wrote:
>> On Sat, Sep 03, 2011 at 10:19:57PM -0400, Ken Brown wrote:
>>> Building setup.exe fails as follows:
>>>
>>> depbase=`echo archive.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
>>> i686-pc-mingw32-g++ -DPACKAGE_NAME=\"setup\" 
>>> -DPACKAGE_TARNAME=\"setup\" -DPACKAGE_VERSION=\"0\" 
>>> -DPACKAGE_STRING=\"setup\ 0\" -DPACKAGE_BUGREPORT=\"xxx\" 
>>> -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
>>> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
>>> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
>>> -DLT_OBJDIR=\".libs/\" -DHAVE_LIBMINGW32=1 -DHAVE_ERRNO_H=1 -DHAVE_STRING=1 
>>> -DHAVE_STRING_H=1 -I.  -DLZMA_API_STATIC -I./libgetopt++/include  -Werror 
>>> -Wall -Wno-uninitialized -Wpointer-arith -Wcomments -Wcast-align 
>>> -Wwrite-strings -g -O2 -MT archive.o -MD -MP -MF $depbase.Tpo -c -o 
>>> archive.o archive.cc&&\
>>> mv -f $depbase.Tpo $depbase.Po
>>> In file included from archive.cc:26:0:
>>> io_stream.h:37:21: error: conflicting declaration ??typedef long int 
>>> ssize_t??
>>> /usr/i686-pc-mingw32/sys-root/mingw/include/sys/types.h:118:18: error: 
>>> ??ssize_t?? has a previous declaration as ??typedef _ssize_t ssize_t??
>>>
>>> The conflicting declarations result from the following recent change to the 
>>> mingw-runtime package:
>>>
>>> 2011-08-19  Chris Sutcliffe
>>>
>>> * include/sys/types.h (ssize_t): Defined as int as opposed to long.
>>>
>>> The following patch enables the build to complete, but I don't know if it's 
>>> the right way to fix this:
>>>
>>> --- io_stream.h.orig2009-12-18 06:59:54.0 -0500
>>> +++ io_stream.h 2011-09-03 21:14:44.664235000 -0400
>>> @@ -33,7 +33,7 @@
>>>   */
>>>
>>> //Where is this defined?
>>> -#if defined(_WIN32)&&  ! defined(__CYGWIN__)
>>> +#if defined(_WIN32)&&  ! defined(__CYGWIN__)&&  ! defined(HAVE_SYS_TYPES_H)
>>> typedef signed long ssize_t;
>>> #endif
>>
>> That's definitely the wrong approach to fix the problem.
>>
>> Why not just include sys/types.h in io_stream.h?
>
>You mean just do this?
>
>--- io_stream.h.orig2009-12-18 06:59:54.0 -0500
>+++ io_stream.h 2011-09-07 07:49:04.458548000 -0400
>@@ -32,10 +32,7 @@
>   * make mkdir_p fit in the hierarchy
>   */
>
>-//Where is this defined?
>-#if defined(_WIN32) && ! defined(__CYGWIN__)
>-typedef signed long ssize_t;
>-#endif
>+#include 
>
>  #if __GNUC__
>  #define _ATTR_(foo) __attribute__ foo

Yes.  I was testing that change after I saw your original mail.  It was
checked in yesterday.

FYI.

cgf


Re: Building setup.exe: conflicting declarations of ssize_t

2011-09-07 Thread Ken Brown

On 9/6/2011 9:52 PM, Christopher Faylor wrote:

On Sat, Sep 03, 2011 at 10:19:57PM -0400, Ken Brown wrote:

Building setup.exe fails as follows:

depbase=`echo archive.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
i686-pc-mingw32-g++ -DPACKAGE_NAME=\"setup\" -DPACKAGE_TARNAME=\"setup\" -DPACKAGE_VERSION=\"0\" 
-DPACKAGE_STRING=\"setup\ 0\" -DPACKAGE_BUGREPORT=\"xxx\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
-DLT_OBJDIR=\".libs/\" -DHAVE_LIBMINGW32=1 -DHAVE_ERRNO_H=1 -DHAVE_STRING=1 -DHAVE_STRING_H=1 -I.  -DLZMA_API_STATIC -I./libgetopt++/include  
-Werror -Wall -Wno-uninitialized -Wpointer-arith -Wcomments -Wcast-align -Wwrite-strings -g -O2 -MT archive.o -MD -MP -MF $depbase.Tpo -c -o archive.o 
archive.cc&&\
mv -f $depbase.Tpo $depbase.Po
In file included from archive.cc:26:0:
io_stream.h:37:21: error: conflicting declaration ??typedef long int ssize_t??
/usr/i686-pc-mingw32/sys-root/mingw/include/sys/types.h:118:18: error: 
??ssize_t?? has a previous declaration as ??typedef _ssize_t ssize_t??

The conflicting declarations result from the following recent change to the 
mingw-runtime package:

2011-08-19  Chris Sutcliffe

* include/sys/types.h (ssize_t): Defined as int as opposed to long.

The following patch enables the build to complete, but I don't know if it's the 
right way to fix this:

--- io_stream.h.orig2009-12-18 06:59:54.0 -0500
+++ io_stream.h 2011-09-03 21:14:44.664235000 -0400
@@ -33,7 +33,7 @@
  */

//Where is this defined?
-#if defined(_WIN32)&&  ! defined(__CYGWIN__)
+#if defined(_WIN32)&&  ! defined(__CYGWIN__)&&  ! defined(HAVE_SYS_TYPES_H)
typedef signed long ssize_t;
#endif


That's definitely the wrong approach to fix the problem.

Why not just include sys/types.h in io_stream.h?


You mean just do this?

--- io_stream.h.orig2009-12-18 06:59:54.0 -0500
+++ io_stream.h 2011-09-07 07:49:04.458548000 -0400
@@ -32,10 +32,7 @@
  * make mkdir_p fit in the hierarchy
  */

-//Where is this defined?
-#if defined(_WIN32) && ! defined(__CYGWIN__)
-typedef signed long ssize_t;
-#endif
+#include 

 #if __GNUC__
 #define _ATTR_(foo) __attribute__ foo

Ken


Re: Building setup.exe: conflicting declarations of ssize_t

2011-09-06 Thread Christopher Faylor
On Sat, Sep 03, 2011 at 10:19:57PM -0400, Ken Brown wrote:
>Building setup.exe fails as follows:
>
>depbase=`echo archive.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
>i686-pc-mingw32-g++ -DPACKAGE_NAME=\"setup\" 
> -DPACKAGE_TARNAME=\"setup\" -DPACKAGE_VERSION=\"0\" -DPACKAGE_STRING=\"setup\ 
> 0\" -DPACKAGE_BUGREPORT=\"xxx\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBMINGW32=1 -DHAVE_ERRNO_H=1 
> -DHAVE_STRING=1 -DHAVE_STRING_H=1 -I.  -DLZMA_API_STATIC 
> -I./libgetopt++/include  -Werror -Wall -Wno-uninitialized -Wpointer-arith 
> -Wcomments -Wcast-align -Wwrite-strings -g -O2 -MT archive.o -MD -MP -MF 
> $depbase.Tpo -c -o archive.o archive.cc &&\
>mv -f $depbase.Tpo $depbase.Po
>In file included from archive.cc:26:0:
>io_stream.h:37:21: error: conflicting declaration ??typedef long int ssize_t??
>/usr/i686-pc-mingw32/sys-root/mingw/include/sys/types.h:118:18: error: 
>??ssize_t?? has a previous declaration as ??typedef _ssize_t ssize_t??
>
>The conflicting declarations result from the following recent change to the 
>mingw-runtime package:
>
>2011-08-19  Chris Sutcliffe  
>
>   * include/sys/types.h (ssize_t): Defined as int as opposed to long.
>
>The following patch enables the build to complete, but I don't know if it's 
>the right way to fix this:
>
>--- io_stream.h.orig2009-12-18 06:59:54.0 -0500
>+++ io_stream.h 2011-09-03 21:14:44.664235000 -0400
>@@ -33,7 +33,7 @@
>  */
>
> //Where is this defined?
>-#if defined(_WIN32) && ! defined(__CYGWIN__)
>+#if defined(_WIN32) && ! defined(__CYGWIN__) && ! defined(HAVE_SYS_TYPES_H)
> typedef signed long ssize_t;
> #endif

That's definitely the wrong approach to fix the problem.

Why not just include sys/types.h in io_stream.h?

cgf


Re: Building setup.exe

2003-08-20 Thread Max Bowsher
Mark Blackburn wrote:
> Where are the instructions for building setup? Are they in a FAQ
> somewhere or in the source tree? For that matter how do you figure out
> to get the source from cvs?
> 
> I already know some of these answers ie:
> cvs -d :pserver:[EMAIL PROTECTED]:/cvs/cygwin-apps co setup
> cd setup
> ./bootstrap.sh
> cd ..
> mkdir build
> cd build
> ../setup/configure 
> make
> 
> I figured this much out by stumbling around blindly. I was wondering if
> there was an easy to find reference on cygwin.com somewhere that I can
> use when I forget some of this stuff.

http://sources.redhat.com/cygwin-apps/setup.html

Max.



Re: Building setup.exe

2003-07-24 Thread Max Bowsher
Morrison, John wrote:
> Max Bowsher wrote:
>> Morrison, John wrote:
>>> Max Bowsher wrote:
 Morrison, John wrote:
> $ make release
> compiling messages
> 
> windres --preprocessor "gcc -mno-cygwin -E -xc-header -DRC_INVOKED"
> --include-dir . -o res.o res.rc
> make: *** No rule to make target `zlib/libzcygw.a', needed by
> `setup.exe'. Stop.
> 
> Oops :)  What's next?  (or should I not make release first?)
 
 Right.
>>> 
>>> Err, right?  Right what?  What do I need to do to get an exe?
>> 
>> Well, *yes*, you shouldn't run make release first. Do "make".
> 
> Doh!  Sorry, am (obviously) not feeling too bright this morning.
> Take my advice; don't accept any patches from me without *REALLY*
> going through it! ;)
> 
> Thanks, everything works now.  Do you want me to read through your
> revised web page before it goes up?

Initially, I will just trivially edit the sentence about bootstrap.sh.

Any non-trivial changes will be discussed on this list.

Max.



RE: Building setup.exe

2003-07-24 Thread Morrison, John
Max Bowsher wrote:
> Morrison, John wrote:
>> Max Bowsher wrote:
>>> Morrison, John wrote:
 $ make release
 compiling messages
 
 windres --preprocessor "gcc -mno-cygwin -E -xc-header -DRC_INVOKED"
 --include-dir . -o res.o res.rc
 make: *** No rule to make target `zlib/libzcygw.a', needed by
 `setup.exe'. Stop. 
 
 Oops :)  What's next?  (or should I not make release first?)
>>> 
>>> Right.
>> 
>> Err, right?  Right what?  What do I need to do to get an exe?
> 
> Well, *yes*, you shouldn't run make release first. Do "make".

Doh!  Sorry, am (obviously) not feeling too bright this morning.
Take my advice; don't accept any patches from me without *REALLY*
going through it! ;)

Thanks, everything works now.  Do you want me to read through your
revised web page before it goes up?

>> PS, I'm subscribed to -apps, you can remove me from the reply.
>> I'd set the reply to, but I'm limited to Outlook at work and
>> don't know how :|
> 
> Using OE here - haven't yet found another mailer which is both GUI
> and non-hideously ugly. So, I've done it this time, but may not
> always remember. 

Hey, no worries.

Thanks for all the help,

J.


===
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission.  There is no intention to
create any legally binding contract or other commitment through the use
of this email.
Experian Limited (registration number 653331).
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF



Re: Building setup.exe

2003-07-24 Thread Max Bowsher
Morrison, John wrote:
> Max Bowsher wrote:
>> Morrison, John wrote:
>>> $ make release
>>> compiling messages
>>>
>>> windres --preprocessor "gcc -mno-cygwin -E -xc-header -DRC_INVOKED"
>>> --include-dir . -o res.o res.rc
>>> make: *** No rule to make target `zlib/libzcygw.a', needed by
>>> `setup.exe'. Stop.
>>>
>>> Oops :)  What's next?  (or should I not make release first?)
>>
>> Right.
>
> Err, right?  Right what?  What do I need to do to get an exe?

Well, *yes*, you shouldn't run make release first. Do "make".

> PS, I'm subscribed to -apps, you can remove me from the reply.
> I'd set the reply to, but I'm limited to Outlook at work and
> don't know how :|

Using OE here - haven't yet found another mailer which is both GUI and
non-hideously ugly.
So, I've done it this time, but may not always remember.


Max.



RE: Building setup.exe

2003-07-24 Thread Morrison, John
Max Bowsher wrote:
> Morrison, John wrote:
>> Max Bowsher wrote:
>>> It seems the instructions are out of date.
>>> You need to run ./bootstrap.sh in setup (and it will recurse into
>>> libgetopt++).
>> 
>> bootstrap.sh isn't executable as checkedout of cvs...
> 
> Hmm. Just checked, and libgetopt++/bootstrap.sh isn't either. (Or was
> it for you?) 

Err, didn't check, sorry, I can't remember.  I *might* have changed
this last night without thinking.

> Robert: Shall I tweak this in cvs?

Please, or add it as something to do

>> $ make release
>> compiling messages
>> 
>> windres --preprocessor "gcc -mno-cygwin -E -xc-header -DRC_INVOKED"
>> --include-dir . -o res.o res.rc
>> make: *** No rule to make target `zlib/libzcygw.a', needed by
>> `setup.exe'. Stop. 
>> 
>> Oops :)  What's next?  (or should I not make release first?)
> 
> Right.

Err, right?  Right what?  What do I need to do to get an exe?

(sorry, that might have come across a little mean; but then this
is a cygwin list :D - it wasn't intended)

J.

PS, I'm subscribed to -apps, you can remove me from the reply.
I'd set the reply to, but I'm limited to Outlook at work and
don't know how :|


===
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission.  There is no intention to
create any legally binding contract or other commitment through the use
of this email.
Experian Limited (registration number 653331).
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF



Re: Building setup.exe

2003-07-24 Thread Max Bowsher
Morrison, John wrote:
> Max Bowsher wrote:
>> It seems the instructions are out of date.
>> You need to run ./bootstrap.sh in setup (and it will recurse into
>> libgetopt++).
>
> bootstrap.sh isn't executable as checkedout of cvs...

Hmm. Just checked, and libgetopt++/bootstrap.sh isn't either.
(Or was it for you?)

Robert: Shall I tweak this in cvs?

> $ make release
> compiling messages
>
> windres --preprocessor "gcc -mno-cygwin -E -xc-header -DRC_INVOKED"
> --include-dir . -o res.o res.rc
> make: *** No rule to make target `zlib/libzcygw.a', needed by `setup.exe'.
> Stop.
>
> Oops :)  What's next?  (or should I not make release first?)

Right.


Max.



RE: Building setup.exe

2003-07-24 Thread Morrison, John
Max Bowsher wrote:
> John Morrison wrote:
>> Hi Max,
>> 
>> Please excuse me for writting to you off list, but I
>> am trying to compile the setup app.  Again.
> 
> You are excused,

Thanks :)

> since I definitely want to help people compile
> setup, but I'm redirecting to the list, as this is relevant there,
> too. 

OK, the more the merrier :)

(Although it'll mean more work for you and Rob)

>> I've a full installation of Cygwin, then, using
>>  as a reference...
>> 
>> $ cvs -z3 -d
>> pserver:[EMAIL PROTECTED]:/cvs/cygwin-apps co setup
>> co messages 

$ cd setup

> It seems the instructions are out of date.
> You need to run ./bootstrap.sh in setup (and it will recurse into
> libgetopt++). 

bootstrap.sh isn't executable as checkedout of cvs...

$ chmod 744 bootstrap.sh

>> $ ./bootstrap.sh
>> bootstrap messages
>> 
>> $ ./configure -C --enable-dependencies --disable-shared
>> --host=i686-pc-mingw32
>>  --build=i686-pc-cygwin 'CC=gcc -mno-cygwin'
>> 'CXX=g++ -mno-cygwin' --enable-maintainer-mode

configure messages

$ make release
compiling messages

windres --preprocessor "gcc -mno-cygwin -E -xc-header -DRC_INVOKED"
--include-dir . -o res.o res.rc
make: *** No rule to make target `zlib/libzcygw.a', needed by `setup.exe'.
Stop.

Oops :)  What's next?  (or should I not make release first?)

J.


===
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission.  There is no intention to
create any legally binding contract or other commitment through the use
of this email.
Experian Limited (registration number 653331).
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF



Re: Building setup.exe

2003-07-23 Thread Max Bowsher
John Morrison wrote:
> Hi Max,
>
> Please excuse me for writting to you off list, but I
> am trying to compile the setup app.  Again.

You are excused, since I definitely want to help people compile setup, but
I'm redirecting to the list, as this is relevant there, too.

> I've a full installation of Cygwin, then, using
>  as a
> reference...
>
> $ cvs -z3 -d :pserver:[EMAIL PROTECTED]:/cvs/cygwin-apps co setup
> co messages
>
> $ cd setup/libgetopt++/
> $ ./bootstrap.sh
> bootstrap messages
>
> $ cd ..
> $
>
./configure -C --enable-dependencies --disable-shared --host=i686-pc-mingw32
>  --build=i686-pc-cygwin 'CC=gcc -mno-cygwin'
> 'CXX=g++ -mno-cygwin' --enable-maintainer-mode
> bash: ./configure: No such file or directory
>
> What did I miss out?  Can you help?

It seems the instructions are out of date.
You need to run ./bootstrap.sh in setup (and it will recurse into
libgetopt++).

Robert: May I commit an appropriate re-wording to the webpage?


Max.



RE: building setup.exe -- solved

2002-06-15 Thread Robert Collins



> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of Jan Nieuwenhuizen
> Sent: Friday, 14 June 2002 8:55 PM

> 12:40:55 fred@peder:~/cvs/cygwin/cygwin-apps/setup
> $ diff -u bz2lib/configure.in.orig bz2lib/configure.in
> --- bz2lib/configure.in.orig  Fri Jun 14 12:35:07 2002
> +++ bz2lib/configure.in   Fri Jun 14 12:36:09 2002
> @@ -7,7 +7,7 @@
>  AM_INIT_AUTOMAKE(libbz2, 0.0)
>  AM_MAINTAINER_MODE
>  
> -CPPFLAGS=-U_WIN32
> +CPPFLAGS="$CPPFLAGS -U_WIN32"
>  AC_CANONICAL_HOST
>  AC_PROG_CC
>  AC_PROG_RANLIB

Thanks, I'm applying such a patch to HEAD.

Rob