BGINFO4X writes:
> Is there any way to automate this?
Automate what, the Cygwin install? Yes, BTDT.
> Do the people (port owners) compile all the ports manually each time?
Sort of, if you have many packages there will be some amount of
scripting going on or you'll go insane. Full build automat
Kizito Porta Balanyà writes:
> Which is the best way to compile a program for both platforms (32-64 bits)
> to release a cygwin package?
Depending on how cleanly the sources and build system are set up you
could cross-compile one or the other or even both (from GNU/Linux), but
if you want to run t
On 23/01/2018 21:25, BGINFO4X wrote:
2018-01-23 14:17 GMT+01:00 Marco Atzeri :
On 23/01/2018 19:43, Kizito Porta Balanyà wrote:
2018-01-18 19:47 GMT+01:00 szgyg :
Which is the best way to compile a program for both platforms (32-64 bits)
to release a cygwin package?
Thanks.
to have b
2018-01-23 14:17 GMT+01:00 Marco Atzeri :
> On 23/01/2018 19:43, Kizito Porta Balanyà wrote:
>
>> 2018-01-18 19:47 GMT+01:00 szgyg :
>>
>>
>
>> Which is the best way to compile a program for both platforms (32-64 bits)
>> to release a cygwin package?
>>
>> Thanks.
>>
>>
> to have both 32bit and 64
On 23/01/2018 19:43, Kizito Porta Balanyà wrote:
2018-01-18 19:47 GMT+01:00 szgyg :
Which is the best way to compile a program for both platforms (32-64 bits)
to release a cygwin package?
Thanks.
to have both 32bit and 64bit cygwin installed.
Regards
MArco
--
Problem reports: ht
2018-01-18 19:47 GMT+01:00 szgyg :
> On 2018-01-18, BGINFO4X wrote:
> > 2018-01-17 20:12 GMT+01:00 szgyg :
>
> Please don't quote raw email addresses.
>
> > Finally, fter switching to the 32bits cygwin version (-m32 in cygwin64
> > generated
On 2018-01-18, BGINFO4X wrote:
> 2018-01-17 20:12 GMT+01:00 szgyg :
Please don't quote raw email addresses.
> Finally, fter switching to the 32bits cygwin version (-m32 in cygwin64
> generated more errors), and modifying Lync.c , monit has b
Hello again,
Yes, you are right, --ansi have undesirable effects like:
In file included from src/net.h:30:0,
from src/p.y:120:
src/monit.h:124:1: error: C++ style comments are not allowed in ISO C90
//FIXME: we can export this type in libmonit
^
etc ...
Finally, fter switching
On 2018-01-15, Brian Inglis wrote:
> On 2018-01-15 13:56, szgyg wrote:
>> On 2018-01-15, Kizito Porta Balanyà wrote:
>>> I'm trying to compile the last version of MONIT and I get some errors that
>>> I can not solve.
>>> :0:6: error: expected identifier or ‘(’ before numeric
>>> constant
>>> src/mo
On 2018-01-15 13:56, szgyg wrote:
> On 2018-01-15, Kizito Porta Balanyà wrote:
>> I'm trying to compile the last version of MONIT and I get some errors that
>> I can not solve.
>> :0:6: error: expected identifier or ‘(’ before numeric
>> constant
>> src/monit.h:581:19: note: in expansion of macro ‘
On 2018-01-15, Kizito Porta Balanyà wrote:
> Hello all,
>
> I'm trying to compile the last version of MONIT and I get some errors that
> I can not solve.
>
> :0:6: error: expected identifier or ‘(’ before numeric
> constant
> src/monit.h:581:19: note: in expansion of macro ‘unix’
>
Hello again,
Well,your are right, I modified the sources to port monit to cygwin, as I
did correctly in version 5.10.
Below you will find a quick how-to (and at the end the required diff files).
##
CYGWIN PACKGAGING
On 1/15/2018 7:22 AM, Kizito Porta Balanyà wrote:
Hello all,
I'm trying to compile the last version of MONIT and I get some errors that
I can not solve.
Basically I get errors like: expected identifier or ‘(’ before numeric
constant, but reviewing the code I don't see any wrong, beside that the
Hello all,
I'm trying to compile the last version of MONIT and I get some errors that
I can not solve.
Basically I get errors like: expected identifier or ‘(’ before numeric
constant, but reviewing the code I don't see any wrong, beside that the
sources compile correctly with Linux, AIX, etc ...
14 matches
Mail list logo
