Project
May I request for your partnership to execute a project in Asia, revert if interested -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: YouCompleteMe build fails: problem with LONG_BIT in pyport.h or ld missing python lib
Whitedwarf tura-home.de> writes: > > Hi all, > > I'm trying to install (i.e., mainly, build) the vim plugin YouCompleteMe > in cygwin64 on a x86_64 machine and got stuck. > > The first error message was > > [ 11%] Building CXX object > BoostParts/CMakeFiles/BoostParts.dir/libs/python/src/converter/ arg_to_python_base.cpp.o > In file included from /usr/include/python2.7/Python.h:58:0, > from > /home/matu_gr/.vim/bundle/YouCompleteMe/cpp/BoostParts/boost/python/ detail/wrap_python.hpp:142, > from > /home/matu_gr/.vim/bundle/YouCompleteMe/cpp/BoostParts/boost/python/ detail/prefix.hpp:13, > from > /home/matu_gr/.vim/bundle/YouCompleteMe/cpp/BoostParts/boost/python/ handle.hpp:8, > from > /home/matu_gr/.vim/bundle/YouCompleteMe/cpp/BoostParts/boost/python/ converter/arg_to_python_base.hpp:7, > from > /home/matu_gr/.vim/bundle/YouCompleteMe/cpp/BoostParts/libs/python/src/ converter/arg_to_python_base.cpp:6: > /usr/include/python2.7/pyport.h:886:2: Fehler: #error "LONG_BIT > definition appears wrong for platform (bad gcc/glibc config?)." > #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc > config?)." > ^ > BoostParts/CMakeFiles/BoostParts.dir/build.make:402: recipe for target > 'BoostParts/CMakeFiles/BoostParts.dir/libs/python/src/converter/ arg_to_python_base.cpp.o' > failed > make[3]: *** > [BoostParts/CMakeFiles/BoostParts.dir/libs/python/src/converter/ arg_to_python_base.cpp.o] > Error 1 > CMakeFiles/Makefile2:78: recipe for target > 'BoostParts/CMakeFiles/BoostParts.dir/all' failed > make[2]: *** [BoostParts/CMakeFiles/BoostParts.dir/all] Error 2 > CMakeFiles/Makefile2:212: recipe for target > 'ycm/CMakeFiles/ycm_support_libs.dir/rule' failed > make[1]: *** [ycm/CMakeFiles/ycm_support_libs.dir/rule] Error 2 > Makefile:148: recipe for target 'ycm_support_libs' failed > make: *** [ycm_support_libs] Error 2 > > I've tried to work around with (as mentioned in > https://github.com/Valloric/YouCompleteMe/issues/66 ) > > -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 > -DPYTHON_LIBRARY=/usr/lib/libpython2.7.dylib > > but this did not help. (CMake configuration reports the same libs if not > provided explicitly anyway.) > > Then I've tried to reset the compilers CMake uses: using > -DCMAKE_C_COMPILER and -DCMAKE_CXX_COMPILER, I've set the compilers > first to /usr/bin/x86_64-pc-cygwin-gcc and > /usr/bin/x86_64-pc-cygwin-g++, respectively; then to > /usr/bin/i686-pc-cygwin-gcc and /usr/bin/i686-pc-cygwin-g++. But now I get: > > Linking CXX shared library ycm_core.pyd > /usr/lib/gcc/i686-pc-cygwin/4.7.3/../../../../i686-pc-cygwin/bin/ld: > cannot find -lpython2.7 > collect2: Fehler: ld gab 1 als Ende-Status zurück > ycm/CMakeFiles/ycm_core.dir/build.make:390: recipe for target > 'ycm/ycm_core.pyd' failed > make[3]: *** [ycm/ycm_core.pyd] Error 1 > CMakeFiles/Makefile2:168: recipe for target > 'ycm/CMakeFiles/ycm_core.dir/all' failed > make[2]: *** [ycm/CMakeFiles/ycm_core.dir/all] Error 2 > CMakeFiles/Makefile2:212: recipe for target > 'ycm/CMakeFiles/ycm_support_libs.dir/rule' failed > make[1]: *** [ycm/CMakeFiles/ycm_support_libs.dir/rule] Error 2 > Makefile:148: recipe for target 'ycm_support_libs' failed > make: *** [ycm_support_libs] Error 2 > > Do you have any ideas or experience on how to fix this? > > Best regards, > > whitedwarf > > System/versions: win7-64, cygwin64 with cygwin-gcc installed in 32- and > 64-bit versions, https://github.com/Valloric/YouCompleteMe > > I've been having the same problem as you, though YCM compiles fine under 32- bit Cygwin. I don't think that using the i686 compilers is the way to go because, as said at the top of this page (https://github.com/Valloric/ YouCompleteMe/wiki/Windows-Installation-Guide): "Before starting this installation procedure, it's critically important that you understand that the architecture (x86 vs x86-64) that you build ycm_core.pyd for has to match the architecture of the python27.dll on your system and the architecture of the Vim binary you will be running. All three need to match, otherwise things won't work." I have also tried downloading older versions of YCM, up to August 2013, because that's when the author of the YCM installation for Cygwin guide (see link above) wrote his guide. Still the same LONG_INT error. I hope a solution for this emerges. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: YouCompleteMe build fails: problem with LONG_BIT in pyport.h or ld missing python lib
On Dec 19 11:57, D wrote: > Whitedwarf tura-home.de> writes: > > /home/matu_gr/.vim/bundle/YouCompleteMe/cpp/BoostParts/libs/python/src/ > converter/arg_to_python_base.cpp:6: > > /usr/include/python2.7/pyport.h:886:2: Fehler: #error "LONG_BIT > > definition appears wrong for platform (bad gcc/glibc config?)." > > #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc > > config?)." > > ^ > > [...] > > System/versions: win7-64, cygwin64 with cygwin-gcc installed in 32- and > > 64-bit versions, https://github.com/Valloric/YouCompleteMe > > I've been having the same problem as you, though YCM compiles fine under 32- > bit Cygwin. I don't think that using the i686 compilers is the way to go > because, as said at the top of this page (https://github.com/Valloric/ > YouCompleteMe/wiki/Windows-Installation-Guide): > > "Before starting this installation procedure, it's critically important > that you understand that the architecture (x86 vs x86-64) that you build > ycm_core.pyd for has to match the architecture of the python27.dll on your > system and the architecture of the Vim binary you will be running. All > three need to match, otherwise things won't work." > > I have also tried downloading older versions of YCM, up to August 2013, > because that's when the author of the YCM installation for Cygwin guide > (see link above) wrote his guide. Still the same LONG_INT error. > > I hope a solution for this emerges. The solution for this is a bit of header file debugging. Quite obviously, LONG_BIT is defined wrongly at some point in the header files, so you have to find out what part of the project is doing that. Keep in mind that sizeof(long) is 8 on 64 bit Cygwin[1][2]. The test in pyport.h which errors out here is basically this: #ifndef LONG_BIT #define LONG_BIT (8 * SIZEOF_LONG) #endif #if LONG_BIT != 8 * SIZEOF_LONG #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." #endif SIZEOF_LONG is correctly defined as 8 in pyconfig.h. If LONG_BIT would be undefined at this point, pyport.h would correctly define LONG_BIT to 64 here. So it's evident that some other header defines LONG_BIT wrongly, probably to 32, because somebody wrongly assumes that sizeof(long) is always 4 on Cygwin. Corinna [1] http://cygwin.com/faq/faq.html#faq.programming.64bitporting [2] http://cygwin.com/faq/faq.html#faq.programming.64bitporting-fail -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpx9n6eTxrS2.pgp Description: PGP signature
Re: Problems with Cygwin symlinks on a TrueCrypt volume
Corinna, On Wed, 11 Dec 2013 14:53:33 +0100 you wrote: > ... > Apart from that, there's a chance that this is a problem not related > to Cygwin's usage of a transaction on a TrueCrypt volume in the first > place. Can you try the workaround from > http://support.microsoft.com/kb/948252 and see if that fixes the issue > with the release Cygwin DLL 1.7.27? I just did, I opened "cmd.exe" :-(ugh)-:, removed the "*.blf" and "*.regtrans-ms" files as requested, and then rebooted. But it did NOT (repeat _NOT_) solve the problem. And, to be honest, any other result would have greatly surprised me, because I never yet did a System Re- store on my Windows system and I _CAN_ install Windows updates and hot- fixes. So I'm again back to your patched DLL and it is still working great ... :-) Sincerely Rainer -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problems with Cygwin symlinks on a TrueCrypt volume
On Dec 19 15:53, Dr Rainer Woitok wrote: > Corinna, > > On Wed, 11 Dec 2013 14:53:33 +0100 you wrote: > > > ... > > Apart from that, there's a chance that this is a problem not related > > to Cygwin's usage of a transaction on a TrueCrypt volume in the first > > place. Can you try the workaround from > > http://support.microsoft.com/kb/948252 and see if that fixes the issue > > with the release Cygwin DLL 1.7.27? > > I just did, I opened "cmd.exe" :-(ugh)-:, removed the "*.blf" and > "*.regtrans-ms" files as requested, and then rebooted. But it did NOT > (repeat _NOT_) solve the problem. And, to be honest, any other result > would have greatly surprised me, because I never yet did a System Re- > store on my Windows system and I _CAN_ install Windows updates and hot- > fixes. So I'm again back to your patched DLL and it is still working > great ... :-) Thanks for testing and your feedback! So I take it that I should not back out the patch again ;) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpkdgZzXGnGb.pgp Description: PGP signature
Re: Odd command line recall problem
Excellent! I unset HISTIGNORE and use HISTCONTROL to remove duplicates. Also learned something about \t. What was in HISTIGNORE must have been the setup default perhaps, though not necessarily from cygwin, it might be from another bash shell setup. Eric Blake-3 wrote > On 12/18/2013 04:42 PM, buggsy2 wrote: >> Good idea, right now it's: >> >> xyz:/cygdrive/d/>printenv HISTIGNORE >> &:[ \t]*:#* > > This says: > > ignore duplicate commands, > ignore any command starting with space, backslash, or t, > ignore any comment > > and tac starts with 't'. -- View this message in context: http://cygwin.1069669.n5.nabble.com/Odd-command-line-recall-problem-tp105022p105052.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: cygwin texlive problem
On 12/19/2013 10:08 AM, Valerie Livina wrote: Dear Prof. Ken Brown, I apologise, I just sent the email unfinished - I continue it here. I found your email in Cygwin mailing lists, and I understand that you are an expert in TeXLive packages in Cygwin. I would be very grateful if you could help me in my installation problem, or advise me who could I contact regarding this. Your mail should have gone to the Cygwin mailing list. Please send any followups there. I have cygwin32 installed on my computer (running Window7 64-bit). I installed cygwin32 because I need to use xmgrace, which is not yet available in the 64-bit version. I compile a tex-file with some glossary using fonts that are not available in the default TeXLive package and get error message, which is disccussed here: http://tex.stackexchange.com/questions/97123/problem-finding-metafonts-at-compilation I understand that I have to install additional fonts, so I run again Cygwin installer and add the recommended packages, texlive-fonts-extra texlive-fonts-recommended I add these two packages in the Cygwin installer and then it suggests me to choose a server for installation. Are you running setup-x86.exe from the Cygwin website? It should ask you to choose a mirror very early in the process, not after you've selected packages. I have spent two days already trying to get access to most of the servers in the list, and none of them allows me to perform installation. The status bar gets stuck in the middle of Progress, and after some time the installer says that I have to choose another server. It keeps going like this without installing the packages, as if theres is some general problem with installation. Would you please advise how can I solve this problem? At what point does the installation get stuck? Is it during the download? And what's the exact error message that you get? By the way, I don't think your problem has anything to do with TeX Live, except that the packages you're trying to install are moderately large. Do you generally have problems downloading large files? Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: cygwin texlive problem
On 12/19/2013 12:47 PM, Ken Brown wrote: On 12/19/2013 10:08 AM, Valerie Livina wrote: Dear Prof. Ken Brown, I apologise, I just sent the email unfinished - I continue it here. I found your email in Cygwin mailing lists, and I understand that you are an expert in TeXLive packages in Cygwin. I would be very grateful if you could help me in my installation problem, or advise me who could I contact regarding this. Your mail should have gone to the Cygwin mailing list. Please send any followups there. I have cygwin32 installed on my computer (running Window7 64-bit). I installed cygwin32 because I need to use xmgrace, which is not yet available in the 64-bit version. I compile a tex-file with some glossary using fonts that are not available in the default TeXLive package and get error message, which is disccussed here: http://tex.stackexchange.com/questions/97123/problem-finding-metafonts-at-compilation I understand that I have to install additional fonts, so I run again Cygwin installer and add the recommended packages, texlive-fonts-extra texlive-fonts-recommended I add these two packages in the Cygwin installer and then it suggests me to choose a server for installation. Are you running setup-x86.exe from the Cygwin website? It should ask you to choose a mirror very early in the process, not after you've selected packages. I have spent two days already trying to get access to most of the servers in the list, and none of them allows me to perform installation. The status bar gets stuck in the middle of Progress, and after some time the installer says that I have to choose another server. It keeps going like this without installing the packages, as if theres is some general problem with installation. Would you please advise how can I solve this problem? At what point does the installation get stuck? Is it during the download? And what's the exact error message that you get? By the way, I don't think your problem has anything to do with TeX Live, except that the packages you're trying to install are moderately large. Do you generally have problems downloading large files? Also, it's always possible to navigate to the mirror in question (through a browser, for example) and see if the package causing the problem can successfully be downloaded that way. I'm not recommending this as a workaround really. I'm just suggesting it as a diagnostic to try to pinpoint what may be the source of the problem. -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
doc build tool 'fop' seems to be missing
I'm figuring out the definitive list of packages needed to build 32-bit Cygwin DLL and docs. The DLL now builds OK. The docs build fails: /oss/build make | tee make.out [...] Writing cygwin-functions.html for chapter(cygwin-functions) Writing cygwin-api.html for book(cygwin-api) xmlto --skip-validation --with-dblatex html -o faq -m /oss/src/winsup/doc/cygwin.xsl /oss/src/winsup/doc/faq.xml Writing faq.html for article(faq) sed -i 's;;;g' faq/faq.html /oss/src/winsup/doc/bodysnatcher.pl faq/faq.html xsltproc --xinclude /oss/src/winsup/doc/fo.xsl /oss/src/winsup/doc/cygwin-ug-net.xml | fop -q -fo - cygwin-ug-net/cygwin-ug-net.pdf /bin/sh: fop: command not found Making portrait pages on USletter paper (8.5inx11in) make[3]: [cygwin-ug-net/cygwin-ug-net.pdf] Error 127 (ignored) Makefile:61: recipe for target 'cygwin-ug-net/cygwin-ug-net.pdf' failed xsltproc --xinclude /oss/src/winsup/doc/fo.xsl cygwin-api.xml | fop -q -fo - cygwin-api/cygwin-api.pdf /bin/sh: fop: command not found Package Search yields no hits for "/fop$" or "/fop.exe$". The winsup/doc/README doesn't mention fop. I've installed all packages listed in that README. The winsup/doc/ChangeLog mentions fop as now part of the build process, along with xsltproc, in an update dated 2013-07-20. But I can't find fop. Any leads appreciated. Thanks, ..mark -- I'm actually more of a Dapper Dan man. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: doc build tool 'fop' seems to be missing
On Thu, Dec 19, 2013 at 06:47:24PM +, Mark Geisert wrote: >I'm figuring out the definitive list of packages needed to build 32-bit >Cygwin DLL and docs. The DLL now builds OK. The docs build fails: > >/oss/build make | tee make.out >[...] >Writing cygwin-functions.html for chapter(cygwin-functions) >Writing cygwin-api.html for book(cygwin-api) >xmlto --skip-validation --with-dblatex html -o faq -m >/oss/src/winsup/doc/cygwin.xsl /oss/src/winsup/doc/faq.xml >Writing faq.html for article(faq) >sed -i 's;;;g' faq/faq.html >/oss/src/winsup/doc/bodysnatcher.pl faq/faq.html >xsltproc --xinclude /oss/src/winsup/doc/fo.xsl >/oss/src/winsup/doc/cygwin-ug-net.xml | fop -q -fo - >cygwin-ug-net/cygwin-ug-net.pdf >/bin/sh: fop: command not found >Making portrait pages on USletter paper (8.5inx11in) >make[3]: [cygwin-ug-net/cygwin-ug-net.pdf] Error 127 (ignored) >Makefile:61: recipe for target 'cygwin-ug-net/cygwin-ug-net.pdf' failed >xsltproc --xinclude /oss/src/winsup/doc/fo.xsl cygwin-api.xml | fop -q -fo - >cygwin-api/cygwin-api.pdf >/bin/sh: fop: command not found > >Package Search yields no hits for "/fop$" or "/fop.exe$". The >winsup/doc/README doesn't mention fop. I've installed all packages listed >in that README. The winsup/doc/ChangeLog mentions fop as now part of the >build process, along with xsltproc, in an update dated 2013-07-20. But I >can't find fop. Any leads appreciated. You should be getting an "error ignored" when doing a "make". So, you could just ignore the issue. Or: http://cygwin.com/ml/cygwin/2013-11/threads.html#00106 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: doc build tool 'fop' seems to be missing
On 12/19/2013 11:47, Mark Geisert wrote: Package Search yields no hits for "/fop$" or "/fop.exe$". It used to be that you had to get fop from Cygwin Ports. Now it's no longer in Ports, and I don't know why. I thought Yaakov was going to move it to the main Cygwin package repo, due to this core dependency. Maybe that's in the middle of happening right now? Apache FOP is based on Java, so it might not be too tough to get its Unix binary package running under Cygwin's gcj: https://xmlgraphics.apache.org/fop/1.1/ -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Change in behavior of bash / if [
To close the loop: I thought that before hitting "Send" with my response to Eric's latest email, I should check to see if the problem was still happening. I removed the quotes from around x$1 and ran it. The scripts now works as expected. So whatever it was, it was temporary and can no longer be reproduced. Sigh. Eric, thanks for all the time you put into addressing this issue. Best wishes, - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. The following is for the archive in case this comes up again. (Really because I wrote it before I thought to test to see if the behavior had fixed itself.) I don't expect anyone to read it or do anything. Eric Blake sent the following at Wednesday, December 18, 2013 10:28 AM >On 12/18/2013 07:18 AM, Buchbinder, Barry (NIH/NIAID) [E] wrote: if [ "x$1" = xclip ] >>> >>> Yes, this is the correct fix for the improper quotation of the earlier >>> example. >> >> But why would it need quoting unless the first argument unless the >> command line is quoted and might have a space"? It wasn't. It was >> called from a script that was being sourced by a bash interactive shell >> as follows. >> >> lddir clip > >I'd need to see your entire script to know for sure. Perhaps you are >using calls to 'set' or using shell functions, either of which modifies >$1 from the value that you passed on the command line. But the point >remains - your improper quoting of $1 is not a cygwin-specific issue. >> Speculation: Since cygwin1.dll was updated last week, perhaps >> something happened there. > >Less likely. But without seeing your entire script, it's hard to say. >You haven't given anyone else enough to go on. Here are the scripts without the quotes. Both are kept in /BW, which is NOT in the path. ldc is accessed as an alias, set in ~/.bashrc. /BW> alias ldc alias ldc='. /BW/ldc' Background: lddir was written first. It was used to load Windows Explorer in a particular directory that was based on a string provided as an argument. (lddir was written to avoid a lot of effort navigating a directory tree in Explorer.) ldc was written second. It takes a string from the Windows clipboard, finds a substring of the format that lddir is looking for, gets a posix path from lddir based on the substring, changes to the directory of that path, feeds the windows version of that path to the clipboard, and does a bunch of other stuff. (ldc was designed so I could easily get a string from an email and generate a path so I could easily get to the folder where I needed to save it's attachments. Additionally, it move my shell to that directory so I can use cygwin tools on it. Originally it just did the clipboard -> path -> clipboard + cd and with time the "bunch of other stuff" was added. I should probably combine them.) Anyway, thanks for taking interest in this. As I said, I added the quotes and it works so I don't really need this fixed. Best wishes, - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. ldc Description: ldc lddir Description: lddir -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: doc build tool 'fop' seems to be missing
On 2013-12-19 14:33, Warren Young wrote: It used to be that you had to get fop from Cygwin Ports. It's still there. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
