Re: rxvt-20050409-4 compilation issues
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
> src_prep_init_hook() {
> cd ${SRC_DIR}
> apply_patch ${origsrcdir}/${PN}-import-xpm.patch
> }
Does this work by using CVS HEAD as of Monday night[1], copying this
patch to the topdir, and defining PATCH_URI="${PN}-import-xpm.patch"
instead of the hook function?
[1] http://cygwin.com/ml/cygwin/2006-12/msg00667.html
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFi2OzpiWmPGlmQSMRCINZAKD7vE3UTHTi7iTwvg/yY88sKprlAQCgxwsz
KZ9LRJHmIiMfmVpp7gYZ91k=
=nzCm
-END PGP SIGNATURE-
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: gtk2/glib version mismatch?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles Wilson wrote: > Gerritt -- can you update the gtk* packages to 2.10.x? Actually GNOME is mine now; I updated the non-GUI libs a while ago, thinking that the GUI would not be far behind, but I hit a snag. A while ago I started working on modular X11R7, but I couldn't get XWin to find the fonts (search the archives for details). So now I use modular X11R7.1 for the client and the old X11R6.8 server; sounds odd, but it works. The problem is not the API, as that didn't change, but that modular X11R7 is libtooled, and since GTK is also libtooled and built against it, the dependency libs are hardcoded (i.e. /usr/lib/libX11.la vs. - -L/usr/X11R6/lib -lX11). This makes it impossible to build against my GNOME without modular X (missing .la deps will cause libtool link errors), which I didn't feel ready to add to the distro until the server worked also. A while ago I asked for help figuring out the problem, but got no response. Therefore I left things as they were, and moved on to other things. And since I do have a matching glib2 and gtk2, I didn't think of this. If you think you can help, please search the archives for a start, and let me know what you think. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFVuMjpiWmPGlmQSMRAriwAJ42J8S3oxBRhfpJEJXu4rDl64LGpgCdF8T9 tAKhW7+dsgzK4/o5SRLlBfY= =lBzY -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: glut (for X) cannot be compiled without -mno-cygwin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens Seidel wrote: > Yep, you're right. I installed it and now it seems to work better. > It just failed because of a missing __isnand function in libm. Afer > providing (only as a workaround) my own it works flawlessly. __isnand *is* in the current cygwin (1.5.21). (BTW, you don't need to link against libm on cygwin; all those functions are provided by libcygwin itself; libm is present only for compatibility with build systems that expect it.) > Since I was first not sucessful without freeglut, I tried also a mingw build > using -mno-cygwin. Of course I did not expect a proper linking step but it > helped me to make my application more standard conform. > > Nevertheless it seems that this a fragile. So I first failed because > /usr/bin/make.exe was not found. The funny thing is that I could use > /cygdrive/c/usr/bin/make.exe :-) A symlink fixed this. > > Also some header files such as gmp.h could not be found in /usr/include. > Once I added -I/usr/include (which should be the default) I got a lot of > crazy errors. Adding a symlink to a local include directory helped. Sounds like your mounts are seriously messed up. Yaakov Cygwin Ports -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE27e7piWmPGlmQSMRArgnAJ9XzVqzthoc6W726nP+lBoJlHjJpgCfdcDx 8t16rGhEwlYf3kH0kMCd5i8= =vZDE -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: glut (for X) cannot be compiled without -mno-cygwin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens Seidel wrote: > $ g++ -H -g -O2 -I/usr/X11R6/include main.cpp -lglut > . /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/GL/glut.h > > The references to w32api/GL are probably wrong! > Once I omit -I/usr/X11R6/include (or use -mno-cygwin) it works: Is freeglut installed? It appears not. > $ g++ -H -g -O2 main.cpp -lglut > . /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/GL/glut.h > .. /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/GL/gl.h > .. /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/GL/glu.h > ... /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/stddef.h > > Since I want to build an X application I do not want to use w32api/GL or > -mno-cygwin! Any idea? g++ -g -O2 -I/usr/X11R6/include -L/usr/X11R6/lib main.cpp -lglut You need to specify the -L/usr/X11R6/lib also, since that's where the X11 glut library is found. Yaakov Cygwin Ports -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE2SHzpiWmPGlmQSMRAo+sAJ98vY/98a9VCaH0h+3S/nD4WkeH4ACcCjUM qpUg2/gW+ny/gtLx9RMEUpQ= =yydY -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: broken link
Igor Peshansky wrote: > I thought Yaakov was working on becoming one eventually... This was > mostly a hint to him that he may want to take over the other duties of the > X maintainer... But then, I'm not even sure he's subscribed to this list > yet, so the hint may have been premature. I am, but I'm stuck on the server, see: http://cygwin.com/ml/cygwin-apps/2006-06/msg00039.html I don't have sourceware access yet, so if you could please update the relevant webpage, please do so. As for being subscribed to this list, now you know. :-) Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: trying to build against X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
peter360 wrote:
> checking for X... no
> configure: error: Mrxvt requires the X Window System libraries and headers.
>
> I read the configure program. Looks like it is trying to find
> libXt.{a|so|sl} but failed. I did find libXt.dll.a in my installation, but
> not libXt.a. Are they the same thing?
No. libXt.a would be a static library, while libXt.dll.a is an import
library for the shared cygXt-6.dll.
You'll need to patch the configure script to look for
libXt.{a|dll.a|so|sl} instead.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEbQfcpiWmPGlmQSMRAofTAJ9MijO6rEGI32Q0JiDQcAf6U1JXJwCgpAkh
tkAd80FtPCC4551B9463TJ0=
=+zhW
-END PGP SIGNATURE-
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: Questions for previous Cygwin/X maintainers
Alexander Gottwald wrote: > afair "fixed" and "cursor" (cursor.pcf.gz) from lib/X11/fonts/misc. > "fixed" is an alias to > -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1. > > make sure you run these commands in the misc directory in this order: > > mkfontscale > mkfontdir (equals mkfontscale -b -s -l) I'm pretty sure that I have the fonts installed correctly, as the old XWin runs with the new fonts via -fp. On the other hand, the new XWin won't find neither the new fonts nor the old. > This was an issue on textmode mounts which should have been fixed. > Otherwise link binmode.o to XWin.exe That doesn't seem to help. Are there any patches that may not have been applied upstream that I should know about? How about Alan or Colin? This really baffles me, and I'm not sure how to precede right now. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Questions for previous Cygwin/X maintainers
I'm now trying to get XWin from xorg-server-1.0.2 running. I got it to build with a few minor patches, but it can't seem to find the fonts, similar to the FAQ: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof I have all the fonts installed and have run mkfontdir, mkfontscale, and fc-cache on the font directories. I've even tried running /usr/bin/XWin with the old /usr/X11R6/lib/X11/fonts directories (via -fp arg), but it still can't find the fonts. 1) What are the bare minimum fonts required for running XWin? 2) Is mounting the fonts directory necessary? On one machine, on which xorg-x11-6.8.2 was the first version installed, there is no such mount, and yet the old XWin runs. 3) What else can cause X not to init font path? 4) Is there anything else that I should know that may be helpful? Thanks in advance, Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
Christopher Faylor wrote: Our Cygwin/X maintainer seems to have disappeared so it looks like we, once again, are looking for volunteers to be the "go to person" for Cygwin/X. That would mean building new releases, handling problems in this mailing list, and keeping the cygwin-xfree web site up-to-date. I've been working on packaging modular X11 for the last few weeks. I've finished everything relevant in util, proto, lib, data, and most of app; all that's left now is the rest of app, fonts, docs, and xserver. I don't want to commit to this yet, until I manage to get everything packaged and running, but you should know that it's being worked on. You can check my progress at: ftp://sunsite.dk/projects/cygwinports/release/X11/ Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Looking for Cygwin/X maintainer
Charles Wilson wrote: Alan originally planned to migrate any specific changes in the CYGWIN branch over to HEAD: http://cygwin.com/ml/cygwin-xfree/2005-10/msg00122.html "I'll be working on getting whatever changes exist on [the CYGWIN] branchover into the mainline trunk code next." But that statement was made AFTER the 6.8.99.901 test release and there is no indication of whether that actually happened -- or if it was even necessary (it's possible that there were no differences between the CYGWIN branch and the HEAD branch as of 27-Oct-2005). Nor is it known whether any of these CYGWIN-branch-only changes, IF they even exist, were merged to the modular codebase. FWIW, a grep for CYGWIN in the libraries turns up very few source files, but hw/xwin is present in the server source. X.org's 7.0 release contained EXACTLY the same code as their 6.9 release, only in modularized form using autotools instead of imake. However, even tho Alan was able to build a release-candidate for the monolitic 6.9 code on cygwin, it is unknown whether that same code, over in the modularized tree, can be built on cygwin. Are cygwin's autoconf/automake/libtool up to the task? Did the folks who put together the configure.ac and Makefile.am files make any assumptions that are not true for cygwin? Unknown. The following packages need to have '-no-undefined' added to the *_la_LDFLAGS: libXdmcp liblbxutil libXmu libXaw libXevie libXfont libXi libXres. Other issues I've found so far: * libX11: if X_LOCALE is not defined in general, then at least XSetLocale needs to be forced into the library for compatibility with 6.8. * liblbxutil: there's an $(EXEEXT) missing in a custom make rule, and there's an unaccounted dependency on libXdmcp. * libXaw: the install-exec-hook is Linux-specific. Alan's original plan was "To switch to the modular build without a doubt." and not remain on the monolithic (and now frozen/dead/buried) codebase, so the "keep a big patch" method being used by Colin for xming is not applicable. However, it is unknown how much progress Alan and others were able to make in "switching to the modular build" -- never mind adapting the monolithic-oriented release and pakaging scripts. It is unknown how much of Colin's stuff is helpful for cygwin or already ported/merged-into to the modular codebase. The release and packaging scripts -- which do not appear to be publicly available anyway -- need to be modified to work with the modular architecture. It is unknown what the status of that effort is. With the modular system, you can use the g-b-s as well, one for each tarball. See the following for more details: http://xorg.freedesktop.org/wiki/ModularDevelopersGuide X11R7.0 and beyond, according to the xorg folks, is supposed to live in /usr and NOT /usr/X11R6 (and not /usr/X11R7, either). It is unknown what effect this will have on other cygwin packages. generic-build-script based builders will need to change --x-libraries= statements, but beyond that? Runtime effects should be minimal, although folks will need to remove their cygwin-x shortcuts and re-run (a new, updated) X-start-menu-icons.sh. For one, all other packages should be moved ASAP to /usr, and this can precede X11R7.0. The affected packages outside of xorg-x11 itself are: freeglut fvwm ghostscript-x11 gv lesstif nedit openbox tcm tetex-x11 transfig WindowMaker Xaw3d XmHTML xfig xfig-lib xgraph xmon The update to libXft needs to include a postinstall script along the lines of: find /usr/lib -name '*.la' | xargs -r sed -i -e 's:/usr/X11R6/lib/libXft\.la:/usr/lib/libXft\.la:' A similar solution is needed for any other libtool libraries being moved. Also, much of the documentation in the Contributor's Guide would need to change, to reflect new build procedures -- both for "how to make setup.exe-style packages from a modular xorg tree" and "I just want to build and test and have no interest in making release packages". Does anybody even have a clue as to how these instructions would need to change? Has *anybody* tried to build the modular codebase? I've got as far as the necessary utils, and all protos and libs; I haven't got to the server yet. So far it's pretty straight forward, just very tedious. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Qt3 breakage since 1.5.19
Marc Toussaint wrote: > I found your discussion on the broken QT port to cygwin. http://cygwin.com/acronyms/#PPIOSPE I'm redirecting this to the cygwin-xfree list. Please make sure that your mail client respects the Reply-To: address. > I have the same problem with uic: it is producing broken code (it > looks as if half of the file is simply missing) See my post to the cygwin list: http://cygwin.com/ml/cygwin/2006-02/msg00472.html > Is there any solution yet? I'm desparate. Is there any way to undo the > qt3 update with the cygwin installer? AFAIK the problem is with cygwin-1.5.19. You could downgrade cygwin to 1.5.18, but you will also need to downgrade a number of other packages, the current versions of which depend on new features in 1.5.19. Besides that, you could help track down the problem in cygwin itself, so that we have a chance in getting this fixed for 1.5.20. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Qt3 breakage since 1.5.19
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
René Berber wrote:
> Or the change exposed a bug in Qt.
Either way, it was working in 1.5.18 (didn't I already say I'd be
unhappy if my qt3 was broken with 1.5.19?).
> The library is as close as it gets to a regular library, I separated the debug
> info, it's just not optimized.
>
> It would be interesting to test a rebuilt regular library, have you done that?
Actually, now that you mention it...
I was in the middle of building kdelibs-3.5.1 when gcc choked on
uic-generated code (this happened with both 3.3.4 and 3.3.5). So I went
back to rebuild 3.3.4, and now it won't finish either.
g++ -c -pipe -I/usr/include/postgresql/server
- -I/usr/include/postgresql/pgsql -I/usr/include/postgresql/pgsql/server
- -fno-exceptions -DPIC -Wall -W -O2 -D_REENTRANT -DDESIGNER
- -DQT_INTERNAL_XML -DQT_INTERNAL_WORKSPACE -DQT_INTERNAL_ICONVIE
W -DQT_INTERNAL_TABLE -DQT_TABLET_SUPPORT -DQT_NO_DEBUG
- -DQT_THREAD_SUPPORT
- -I/home/Yaakov/src/kde/qt/3/qt-x11-free-3.3.4/.build/mkspecs/cygwin-g++
- -I. -I/usr/include/freetype2 -I../shared -I../uilib -I../../../include
- -I/usr/X11R6/include -I.moc/release-shared-mt/ -o ./listboxeditor.o
listboxeditor.cpp
listboxeditor.cpp:32:7: warning: no newline at end of file
listboxeditor.cpp: In constructor
'ListBoxEditorBase::ListBoxEditorBase(QWidget*, const char*, bool, uint)':
listboxeditor.cpp:32: error: expected identifier at end of input
listboxeditor.cpp:32: error: expected `(' at end of input
listboxeditor.cpp:32: error: expected `{' at end of input
listboxeditor.cpp: At global scope:
listboxeditor.cpp:32: warning: unused parameter 'parent'
listboxeditor.cpp:32: warning: unused parameter 'name'
listboxeditor.cpp:32: warning: unused parameter 'modal'
listboxeditor.cpp:32: warning: unused parameter 'fl'
listboxeditor.cpp:32: warning: unused parameter 'parent'
listboxeditor.cpp:32: warning: unused parameter 'name'
listboxeditor.cpp:32: warning: unused parameter 'modal'
listboxeditor.cpp:32: warning: unused parameter 'fl'
make: *** [listboxeditor.o] Error 1
Looking at the generated listboxeditor.cpp (and at the KDE package), it
seems that uic doesn't compile .ui files correctly, resulting in the
above gcc errors.
Running the uic command to generate this code in gdb, I get a bunch of
SIGSEGV in pthread_mutex* functions in cygwin1.dll, then:
Program received signal SIGSEGV, Segmentation fault.
0x713f33a4 in QRealMutexPrivate::QRealMutexPrivate ()
from
/home/Yaakov/src/kde/qt/3/qt-x11-free-3.3.4/.build/bin/cygqt-mt-3.dll
The offending code is in src/tools/qmutex_unix.cpp (which has absolutely
no changes from 3.3.4 to 3.3.5).
> All those "mutex lock failure" point to the threads implementation. If you
> want
> to go from "what changed in Cygwin's dll" forward, it has to be something in
> threads.
>
> Going the other way, what I tried is using gdb trying to look at what breaks
> the
> program. The worst part is that under gdb they run fine many times, then
> break
> (with the debug library).
>
> Yet another approach could be to do the porting of the newer 3.x/4.x version.
Same story with 3.3.5, but it's still hard-masked unstable on Gentoo, so
I'm holding it back (at least until I see how KDE 3.5 works with it).
Qt4 is totally different and incompatible with qt3 (but will be parallel
installable, once I get working on it). Let's get this working first,
though.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD4sdZpiWmPGlmQSMRApURAKC4SeiVPZJFe9Fbg3U9MjBvl5jDTgCfX9NI
sIjdGmnQKbGmTS5nwhAklVo=
=NNJm
-END PGP SIGNATURE-
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Qt3 breakage since 1.5.19
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 René Berber wrote: > Running Scribus with the debug enabled cygqt-mt-3.dll the program > works fine with no mutex failure message and using the latest Cygwin > snapshot. As mentioned in my reply to Brian, under gdb there are many > SIGSEGV signals received but continuing results in the same behaviour > as above: no problem. > > So there seems to be no regression, there must be something different > btw. the original build environment and my PC. I used the code (build > script, patches and original code) downloaded using setup.exe. OK, we need to get back to this. Now that cygwin-1.5.19-4 is out, I'm seeing the same breakage with qt3-3.3.4: $ scribus Mutex init failure: Device or resource busy [splashscreen shows, gets as far as loading plugins, then:] Mutex init failure: Invalid argument [exits silently] $ convertall [this is a PyQt app. It exits silently also.] But not everything is affected apparently: $ xxdiff file1 file2 Mutex init failure: Device or resource busy [works, just like before] Mutex lock failure: Invalid argument Mutex unlock failure: Invalid argument Mutex destroy failure: Invalid argument 1) Something changed between 1.5.18 and the 20051207 snapshot to break qt3 threading. 2) It should not be necessary to have a debug library in order for ordinary programs to work. 3) A threaded Qt is required for many packages, including KDE, so disabling threading is not a viable option. Ideas? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD4nhCpiWmPGlmQSMRAh9lAKCtvF9//J6zC4KWQsdJN9wiHPd95QCgxerD UYICx6yxX23jjUdxJAChwyg= =SImM -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Mutex lock failure: Resource deadlock avoided
René Berber wrote: Right forum for qt3, wrong forum for kde. The distinction is that qt3 is an official Cygwin package while KDE is from the Cygwin Ports project. Actually, I've just started working on KDE again with 3.5.1, but I never got as far as kwrite. This is probably from the KDE-Cygwin project, and I have no idea how and if their KDE packages (which are mostly old) work with our Qt3. The error after "Resource deadlock avoided" is probably meaningless. My experience with Scribus is that the application silently ended, another (QT3's uic) deadlocked. > The solution I found for Scribus was to recompile QT with debug enabled, the package building failed but the library was produced. Using that QT library results in Scribus working fine... but with uic is another story, a very strange story: sometimes it works, sometimes it doesn't. I haven't debug any further but with gdb it looks like it's a thread problem (the problem seems to be in some inline C++ code that is difficult to work with). So another solution could be to build QT with no thread support (if that makes sense and works). Most packages nowadays require a threaded Qt, including KDE, so this isn't very practical. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: [ANNOUNCEMENT] New Package: perl-Tk-804.027-3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brett Serkez wrote: > Yaakov, PPIOSPE[1]. Redirecting to xfree list. [1] http://cygwin.com/acronyms/#PPIOSPE > Nothing seems to work, it keeps dying with a 'segementation > violation'. My guess is their is a missing dependency in the > packaging When I selected the new package, it added a couple of > libraries, otherwise all is up-to-date. Please carefully read the following before proceeding: http://cygwin.com/problems.html > This simple program doesn't work: [clip] WFM. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDoMZ2piWmPGlmQSMRApk/AJwPakQ9JHtSXdgvOVuwJ51zESviKgCg+fs+ KlfKftUG7QyaFX2bQVG4A5E= =rlRs -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: scribus: cygjpeg-62.dll not found
Christopher Faylor wrote: Sorry but it isn't up to Yaakov to decide if things that aren't part of the cygwin distribution are discussed here. The fact that we advertise other people's cygwin efforts doesn't mean that we are automatically opening up the cygwin mailing list to discuss their efforts. I agree, and I never said that they should be sent here. Cygwin Ports is my (very large) private repository of packages which I have built, including the packages that I contribute to the distro. Those packages which aren't (yet) in the distro are usually due to any of the following reasons: 1) unsufficiently tested (like, right now, GNOME 2.12 is already there) 2) "queued up" due to dependencies not yet in the distro 3) not of general interest 4) lack of time When I start seeing interest on these lists for something that I have on Cygwin Ports, that usually pushes me to ITP it; perl-Tk is a recent example. I may do the same for scribus, once the issues with René are worked out. And (before someone asks) wrt to the first scribus thread started by René, I only continued that discussion here since her problem has to do with qt3 itself, which I maintain *within* the distro. It now appears that she may have found a regression in a recent snapshot due to that discussion too. In any case, I'll try to clarify on my website about questions on my packages, etc. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Mutex init failure trying to run Scribus
René Berber wrote: I tried using cygwin1.dll version 1.5.18 and it works just like you said. Then I downloaded the latest snapshot, version 20051207, and scribus fails as before (no error messages, the one I used as subject is only a warning, nothing). As this is an apparent regression, if you could track this down in the cygwin1.dll, I'm sure Corinna and cgf would like to know about it on the main list. (I, for one, won't be very happy if my programs stop working when 1.5.19 comes out!) I could not build qt3 with debug enabled because the build also fails with a mutex problem. The program uic runs many times in the build succesfully but once it gets stuck with a "Mutex init failure: Invalid argument". I'm unable to use gdb, every time I try gdb on scribus the program is killed at the beginning (before the splash screen appears) while setting a pthread. > In the code (src/tools/qmutex_unix.cpp), as you have already said, the "Mutex ..." messages are only warnings so they were not related to my original problem, the program should run but it doesn't with a recent cygwin1.dll. But those messages and the uic hanging do point out that there are problems with pthreads as used by qt3. This is with 1.5.18 or the snapshot? I haven't seen if the changes to qt from 3.3.4 to 3.3.5 and to 4.0.1 address any of these problems. I've been waiting on 3.3.5 since, when it first came out, it would not get along with KDE 3.4 (or the other way around), and it's still hard-masked in Gentoo. 4.0.1 (and the soon-to-be-released 4.1.0) are entirely different; these will eventually become a qt4 package (parallel installable with our qt3), but only after it stabilizes more. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Mutex init failure trying to run Scribus
René Berber wrote: Nice! I don't get anything, but perhaps it has to do with my setting CYGWIN=error_start:c:/cygwin/bin/dumper.exe (which is not catching anything). FWIW, I'm just running with CYGWIN=server. Thanks. I'll report later if I find something. Please do, and thank you for your help. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Mutex init failure trying to run Scribus
René Berber wrote: You mean Scribus runs anyway? Perhaps I missed something, I didn't see any window or anything else appear. WFM: http://cygwinports.dotsrc.org/screenshots/scribus.jpg Anyway I'm recompiling Scribus from sources, let's see if the invalid argument is catched on the source, probably not but I want to rule out that the version of Cygwin I'm using (one of the snapshots) didn't change something that affected this. FWIW, I built scribus with stock Cygwin 1.5.18-1. I'm almost certain this has to do with Qt itself, not with any individual program. If you're interested in helping look into this, I'd say to grab the qt3-3.3.4-2-src package and try to find the problem there. Wrt what I said earlier about all C++ Qt programs being affected, that appears to be not 100% true: xxdiff (yes, also available at Cygwin Ports) does not show this message; perhaps it doesn't use Qt threads. In any case, I can't do it this minute, but I hope that early next week I can look into this further. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Mutex init failure trying to run Scribus
René Berber wrote: I just installed Scribus from ftp://sunsite.dk/projects/cygwinports, no problem with the install, but when I tried to run it I got the: "Mutex init failure: Invalid argument" after the splash screen displays for a while and the application really starts. Anyone seen this? Any solutions? Yes, I have as well. It seems to happen with all C++ Qt or KDE apps; PyQt apps (e.g. convertall, also available through Cygwin Ports) don't generate this message. Despite the message, the programs seem to run correctly anyways. Now that I know that this is not just a local issue, I'll try researching this further; this would appear to have something to do with the Qt threading code. Thanks for your report. Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: web browser for cgywin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reid Thompson wrote: > links2 http://links.twibright.com/ graphical -- your best bet I have packages of links-2.x available on Cygwin Ports; just add the following server to setup.exe: ftp://sunsite.dk/projects/cygwinports/ Or manually download from /release/links. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDXV0CpiWmPGlmQSMRAotuAKCWuZTxPjwxJc+dTfPfDGAhI47IfACfeCSP XbipXzXdKzt3VACal79maBc= =iX+2 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Xorg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan Hourihane wrote: > Certainly for the RC1 candidate it's going to be based off the > monolithic build, and still in /usr/X11R6. And what are your plans for future releases? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDWR+lpiWmPGlmQSMRAua1AJ9nozHH6Jmd/FpdZNujKeYbFS5OEgCgrogm DSLFP9heLShnxT50sr+42Hk= =hVgl -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: gnome-terminal and vte: works fine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Per Lundberg wrote: > I have managed to get vte and gnome-terminal compiled and running on > Cygwin/XFree. Seems to be working fine also, and it's nice to have when > you are stuck in the Windows world. Attached is the patch for vte (based > on another patch I found on the net, very small modifications to get the > patch to apply with latest vte). vte is a package neccessary for the > compilation of gnome-terminal. I've had posted for a while vte and gnome-terminal on my Cygwin Ports repository[1], with the vte patch based on the Cygwin Gnome2 project. [1] ftp://sunsite.dk/projects/cygwinports/ > gnome-terminal compiles right out of the box (2.12.0, latest version) > but there is some problems with the help files (because of missing > scrollkeeper-preinstall). If you go into each of the help/XX > subdirectories and run a manual "make gnome-terminal-XX.omf.out", it > will generate these files anyway, but I have not tested whether the > online help works or not. scrollkeeper is also available via Cygwin Ports. > I hope this makes someone happy. :-) How do we now go ahead and get > these packages into the netinstaller? My progress in adding GNOME packages into the net release has been slowed somewhat due to other requisite packages which have yet to be updated in the release. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDWBdfpiWmPGlmQSMRAnOjAKCcm/6aENG2LVwz2FLrpb/RjuUfggCgjcli 31CZEXMVTUWEJNbQNxPmqOE= =Cu+Y -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Xorg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan Hourihane wrote: > Seeing as X.Org has just released their 6.9/7.0 RC1 candidate release > I'm currently building it for a test release for Cygwin/X. > > I'll announce it more formally when I've completed the packaging and > uploaded to the relevant sites. > > If people can test this it'll ensure we can make the transition much > more smoothly. Are you using the 7.0 libtoolized packages? And what about a move to prefix=/usr? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDWBPppiWmPGlmQSMRAke3AKDHT5lx0vbOv/BSpZfFHX4aMKEhFQCg/wcL 9RdjxwpgO0YGiNF8pmYGnHY= =sHUG -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: how to install dillo on cygwinX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles Li wrote: > I would like to install dillo browser on cygwinx. Is > there a document one of you can point me to? Or a > general page for installing softwares on cygwinX. Dillo is not in the Cygwin net release, but I have built a port for Cygwin/X. Please note that bookmarks and downloads do NOT currently work with this port; PTC. Add the following address to your server list in setup.exe: ftp://sunsite.dk/projects/cygwinports/ Or for manual download: ftp://sunsite.dk/projects/cygwinports/release/dillo/ Dillo is listed in the Web and X11 categories. Yaakov Cygwin Ports -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDWBOIpiWmPGlmQSMRAncMAJ423yIATVvsJkl45x/OmM2rG69kxgCgkzUB i6SE4mCp4pX5Pe0uOIwyjeY= =5r3m -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Consensus about man and doc X11 directory structure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles Wilson wrote: > Not gonna happen: it has been stated before on this list that 'insight' > *must* run without X -- which means that tk will remain Win32GUI. Tk must remain Win32GUI, or *a* Win32GUI Tk must remain, for the sake of insight? > It may be possible, eventually, to have both win32GUI-cygwin-runtime-tk > and XGUI-cygwin-runtime-tk on the same machine, but nobody has > undertaken the daunting task to make that happen. Ditto gtk. Others have mentioned building *NIX tcl/tk on Cygwin, and I wouldn't call building gtk2 daunting; I'm not personally interested, as I'm focusing on the X11 ports. > However, I don't see the problem in assuming that GUI apps are presumed > to be X-flavor (with the tk exception, above). If at some point > somebody figures out how to build a similar GUI app/toolkit in the > opposite flavor, it can go in /opt/. What's stopping us from moving the Win32 tcltk in /opt/win32, and making new *NIX tcl and tk packages in /usr? Then all that's necessary for insight is to add /opt/win32 to PATH (either through a script, profile.d, or manually). Similar packages (i.e. that have both X11/*NIX and Win32 flavors) could use /opt/win32 as well. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDSyMSpiWmPGlmQSMRAlCrAJwOhWNKN88hXnK+UasAHCeCDDpBhQCgtjSE LrtlZOCNUN3xcI1gQoT0VFw= =Yz4+ -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Consensus about man and doc X11 directory structure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Ford wrote: > Why do you propose keeping a distinct X11R6 tree yet puting documentation > outside it. I would prefer these to be consistent. FWIW, Debian and Gentoo both do as proposed. > IIRC, Harold had decided to eliminate the X11R6 subtree and cgf agreed. I > guess that was the direction Xorg and several Linux distros were taking. Gentoo did this already with X11R6.8.2. I would agree, with the upcoming modular, autotooled X11R7, that the whole reason for the /usr/X11R6 exception to the FHS no longer applies. > IMHO, that was not desirable. Eventually I could imagine X11 and > Cygwin native versions of the same package. I liked this method of making > the distinction. What does "Cygwin native" mean? If Cygwin is meant to be a POSIX environment, then X11 should be the standard for GUI apps. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDSxA9piWmPGlmQSMRAuwZAKDT0/fkqzHEkuTcXba3eAq5ugQdEwCfdFmN 7TlTParj9ElUf0IGi1wFWVc= =5BME -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
