Re: Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)]

[Yaakov Selkowitz]

On Mon, 2020-04-06 at 23:55 +, JonY via Cygwin wrote:
> On 4/6/20 10:07 AM, Jan Nijtmans via Cygwin wrote:
> > Ping.
> > 
> > Would it be possible to release a version of mingw64-i686-binutils with the
> > same patch as done for binutils-2.34+1git.de9c1b7cfe-1? I suspect
> > this would resolve the problem described here.
> 
> Can you please report this issue to the binutils mailing list? I am
> unfamiliar with the binutils internals to know what exactly went wrong.

JonY,

I think the relevant differences after 2.34 were PR24511 and PR25447,
which are already fixed upstream:

https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=40bfb9762747f8336b17c70a0173d10200fa62eb
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=82f439d028c65663a0baf0a17ef5c4a2ea5c84a7

Adding those as patches to 2.34 should fix the issue without having to
resort to a git snapshot.

--
Yaakov


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)]

[JonY via Cygwin]

On 4/6/20 10:07 AM, Jan Nijtmans via Cygwin wrote:
> Ping.
> 
> Would it be possible to release a version of mingw64-i686-binutils with the
> same patch as done for binutils-2.34+1git.de9c1b7cfe-1? I suspect
> this would resolve the problem described here.
> 
> Thanks!
>Jan Nijtmans

Can you please report this issue to the binutils mailing list? I am
unfamiliar with the binutils internals to know what exactly went wrong.



signature.asc
Description: OpenPGP digital signature
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: cygport requires same package twice?

[Brian Inglis]

On 2020-04-06 14:36, Marco Atzeri via Cygwin wrote:
> Am 06.04.2020 um 22:18 schrieb Åke Rehnman via Cygwin:
>> After running cygport package I get for one of my packages the same
>> dependency twice:
>> libftdi1 requires: bash cygwin libconfuse1 libgcc1 libstdc++6 libusb1.0 
>> libconfuse1
>> Any ideas why? Is it a problem?

> not a problem.
> It is likely due to the duplication of PKG_REQUIRES and cygport detections of
> needed library

...or specified in some PKG.cygport ...REQUIRES=..., so as cygport is so smart,
you can just remove that explicit library package dependency from PKG.cygport
...REQUIRES=..., and rerun cygport PKG.cygport package/-test step.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: cygport requires same package twice?

[Marco Atzeri via Cygwin]

Am 06.04.2020 um 22:18 schrieb Åke Rehnman via Cygwin:

Hello all,

After running cygport package I get for one of my packages the same 
dependency twice:


 >>> libftdi1 requires: bash cygwin libconfuse1 libgcc1 libstdc++6 
libusb1.0 libconfuse1


Any ideas why? Is it a problem?

BR

/Ake



not a problem.

It is likely due to the duplication of
PKG_REQUIRES and cygport detections of needed library


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

cygport requires same package twice?

[Åke Rehnman via Cygwin]

Hello all,

After running cygport package I get for one of my packages the same 
dependency twice:


>>> libftdi1 requires: bash cygwin libconfuse1 libgcc1 libstdc++6 
libusb1.0 libconfuse1


Any ideas why? Is it a problem?

BR

/Ake

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

[ANNOUNCEMENT] pkgconf 1.6.3-1

[Yaakov Selkowitz]

The following packages have been uploaded to the Cygwin distribution:

* pkgconf-1.6.3-1
* libpkgconf3-1.6.3-1
* libpkgconf-devel-1.6.3-1
* pkg-config-1.6.3-1

pkgconf is a program which helps to configure compiler and linker flags 
for development frameworks.  It is an alternative to pkg-config.

This is an update to the latest upstream release.  The cross-pkg-config 
commands have been switched to symlinks based on upstream advice.

--
Yaakov

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: Mingw pkg-config not working

[Yaakov Selkowitz]

On Sun, 2020-04-05 at 15:51 +0200, Carlo B. via Cygwin wrote:
> I wanted to report that I received a reply on the issue that I had opened 
> here:
> 
> https://todo.sr.ht/~kaniini/pkgconf/10#comment-7894

Thanks for following up.

> The report has been closed and I got this reply:
> 
> "You should use a symlink instead of a wrapper script when using the
> personality feature."
> 
> I hope that somebody has understood what he means (posix is not
> exactly my primary platform) and it could be useful for fixing the
> issue.

Yes, that gave me the information I needed.  There is actually code
within pkgconf to automatically load $PREFIX.personality when called as
$PREFIX-pkg-config.  This requires a packaging change on our end, which
I'm incorporating into the latest release.

> Il giorno gio 26 mar 2020 alle ore 14:07 Carlo B.
>  ha scritto:
> > Hello,
> > I implemented the solution to this problem as a patch to
> > pkgconf.cygport as requested.
> > I attached small patch to this email, which resolved the troubles with
> > CMake and Meson.
> > I hope that you will find it useful and  some developers will gently
> > apply the correction to fix the issue.
> > 
> > Thank you very much for your time and your support.
> > Sincerely,
> > 
> > Carlo Bramini.
> > 
> > Il giorno sab 22 feb 2020 alle ore 18:47 Jon Turney
> >  ha scritto:
> > > On 20/02/2020 11:06, Carlo B. wrote:
> > > [...]
> > > > x86_64-w64-mingw32-pkg-config are emulated with a shell script, for
> > > > example the one for i686 is:
> > > > 
> > > > #!/bin/sh
> > > > exec pkgconf --personality=i686-w64-mingw32 $@
> > > > 
> > > > But while this solution mostly works when you exec it from the command
> > > > line, it makes impossible to detect the presence of the tool from
> > > > meson and cmake build systems.
> > > > If you try to do this on the bash prompt, you get:
> > > > 
> > > > $ i686-w64-mingw32-pkg-config --version
> > > > pkgconf: --version specified with other options or module names,
> > > > assuming --modversion.
> > > > Please specify at least one package name on the command line.
> > > > 
> > > > and this is exactly what happens with those build systems (and perhaps
> > > > others, I don't know): it tries to call pkg-config with "--version"
> > > > and it executes the above script that calls pkgconf. But sadly, the
> > > > presence of the "--personality" option makes the process to fail,
> > > > because the "--version" is currently allowed only when no other
> > > > options are added.
> > > > And, for this reason, meson and cmake fail the detection of the tool.
> > > > 
> > > > I have also filed an issue here for pkgconf:
> > > > https://todo.sr.ht/~kaniini/pkgconf/10
> > > > because the solution is actually to ignore the presence of the
> > > > "--personality" option when the "--version" is written, but
> > > > unfortunately I have not received any feedback.
> > > > 
> > > > So, I'm also writing here, with the hope that you could find a solution.
> > > [...]
> > > 
> > > Thanks for reporting this issue.
> > > 
> > > I guess the alternative to fixing pkgconf would be to modify those
> > > wrapper scripts to detect when the parameters are just '--version' (or
> > > equivalent) and not use --personality in that case?
> > > 
> > > These wrapper scripts are specific to cygwin (generated by the cygport,
> > > see [1])
> > > 
> > > It's possible other distros have more sophisticated wrapper scripts,
> > > which avoid this problem?
> > > 
> > > If you do write or discover some improved wrapper scripts, a patch to
> > > [1] to update them would be appreciated.
> > > 
> > > [1]
> > > https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/pkgconf.git;a=blob;f=pkgconf.cygport#l84

--
Yaakov


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: Naming conventions for python packages

[Marco Atzeri via Cygwin]

Am 06.04.2020 um 16:35 schrieb Åke Rehnman via Cygwin:

Hello all,

Sorry if this question is covered somewhere else...  I did try googling...

What are the naming conventions for python packages ?

python2-libftdi1-1.4-1

or

python27-libftdi1-1.4-1

or just

python-libftdi1-1.4-1

Same for python 3:

python3-libftdi1-1.4-1

or

python3.6-libftdi1-1.4-1


BR

/Ake



I suggest

python27-libftdi1-1.4-1
python36-libftdi1-1.4-1

assumimg your library is dependent from the shared lib
of the same python package:


$ cygcheck -l python36 | grep dll
/usr/bin/libpython3.6m.dll



 $ cygcheck -l python27 | grep dll
/usr/bin/libpython2.7.dll
...


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Naming conventions for python packages

[Åke Rehnman via Cygwin]

Hello all,

Sorry if this question is covered somewhere else...  I did try googling...

What are the naming conventions for python packages ?

python2-libftdi1-1.4-1

or

python27-libftdi1-1.4-1

or just

python-libftdi1-1.4-1

Same for python 3:

python3-libftdi1-1.4-1

or

python3.6-libftdi1-1.4-1


BR

/Ake

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)]

[Jan Nijtmans via Cygwin]

Ping.

Would it be possible to release a version of mingw64-i686-binutils with the
same patch as done for binutils-2.34+1git.de9c1b7cfe-1? I suspect
this would resolve the problem described here.

Thanks!
   Jan Nijtmans

Op wo 1 apr. 2020 om 13:33 schreef Jan Nijtmans :
>
> > The following packages have been uploaded to the Cygwin distribution:
> >
> > * binutils-2.34+1git.de9c1b7cfe
> >
> > This release should fix libtool shared library builds on 32bit Cygwin.
>
> When building latest Tcl/Tk 8.6.10 on Cygwin and Win32, I noted that
> on mingw64-i686 the built executables crash immediately. Reverting
> mingw64-i686-binutils from version 2.34-1 back to version
> 2.13.1.be46fa23-1 makes the build work again.
>
> So, it looks like binutils for mingw64 (32-bit only) has the same
> problem as the Cygwin-32 version.
>
> Would it be possible to re-build mingw64-i686-binutils with
> the same patch?
>
> Regards,
> Jan Nijtmans
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: Compilation problem

[cygwinautoreply--- via Cygwin]

>Hello,  I am a user of ALOGRAF 5, and once I have created my Application, I
>cannot compile it. I have this message:
>"












>*4 [main] make 16532 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>pointer.  Please report this problem tothe public mailing list
>cygwin@cygwin.com make[1]: Entering directory
>`/cygdrive/d/PROJET/Appli/NanOpral-1'--- 001.ogenerated/001.c: In
>function 'Grafcet_1_32769':generated/001.c:26:3: error: 'Voyant' undeclared
>(first use in this function)generated/001.c:26:3: note: each undeclared
>identifier is reported only once for each function it appears
>ingenerated/001.c: In function 'Grafcet_1_1':generated/001.c:36:6: error:
>'Bp' undeclared (first use in this function)generated/001.c:36:10: error:
>expected ')' before ';' tokengenerated/001.c:38:3: error: 'Voyant'
>undeclared (first use in this function)make[1]: ***
>[generated/generated/001.o] Error 1make[1]: Leaving directory
>`/cygdrive/d/PROJET/Appli/NanOpral-1'mingw32-make: *** [all] Error 2*


>Please help me (I have Windows 10 x64)  .

>Cordialement ,
>*SOW Souleymane*
>Etudiant en Master Energie Electrique, Electronique, Automatique
>Université Jean Monnet de Saint-Etienne
>Tel: +33 7 60-07-58-73
>Email: *ssouleymane.sow@gmail.com *
>Adresse: 1, Place Paul Gauguin 42300 Roanne

>
>Garanti
>sans virus. www.avast.com
>
><#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Compilation problem

[Souleymane SOW via Cygwin]

Hello,  I am a user of ALOGRAF 5, and once I have created my Application, I
cannot compile it. I have this message:
"












*4 [main] make 16532 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
pointer.  Please report this problem tothe public mailing list
cygwin@cygwin.com make[1]: Entering directory
`/cygdrive/d/PROJET/Appli/NanOpral-1'--- 001.ogenerated/001.c: In
function 'Grafcet_1_32769':generated/001.c:26:3: error: 'Voyant' undeclared
(first use in this function)generated/001.c:26:3: note: each undeclared
identifier is reported only once for each function it appears
ingenerated/001.c: In function 'Grafcet_1_1':generated/001.c:36:6: error:
'Bp' undeclared (first use in this function)generated/001.c:36:10: error:
expected ')' before ';' tokengenerated/001.c:38:3: error: 'Voyant'
undeclared (first use in this function)make[1]: ***
[generated/generated/001.o] Error 1make[1]: Leaving directory
`/cygdrive/d/PROJET/Appli/NanOpral-1'mingw32-make: *** [all] Error 2*


Please help me (I have Windows 10 x64)  .

Cordialement ,
*SOW Souleymane*
Etudiant en Master Energie Electrique, Electronique, Automatique
Université Jean Monnet de Saint-Etienne
Tel: +33 7 60-07-58-73
Email: *ssouleymane.sow@gmail.com *
Adresse: 1, Place Paul Gauguin 42300 Roanne


Garanti
sans virus. www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple