You can subscribe to this list. Erik van Pienbroek schreef op za om 21:21 +0100: JonY schreef op za om 20:35 +0800: On 1/30/2015 08:10, Erik van Pienbroek wrote: All in all I see no blocking issues in mingw-w64 v4.0rc1.
OK, will go ahead with v4.0.0 shortly if there are no objections. Is there still interest in doing another test mass rebuild against the latest gcc 5 snapshot before releasing mingw-w64 v4.0? Attachments: How about the attached patch? It ensures that POSIXTHREADSAFEFUNCTIONS is defined if we declare.r functions. This conforms POSIX better and you may simply detect those functions in the code using this macro.
Windows media player for windows 8 1 free download - Apple Safari, Windows Media Player, Windows Media Player (64-bit), and many more programs. And many more programs. Windows media player for windows 8 1 free download - Apple Safari, Windows Media Player, Windows Media Player (64-bit), and many more programs. There is also a windows version at but I don't. You have to 'run as admin' on windows to access the PCI registers.
You said on IRC that all those changes are needed because VLC maintainer wants mingw-w64 to be POSIX compatible, would that make him happy? Unfortunately No. Localtimer and gmtimer are discovered with ACREPLACEFUNCS in autotools I submitted this patch but it was rejected because he said that localtimer and gmtimer should not be inline as that breaks the spec so he won't accept any kind of work around and that we should comply with the spec. He said that is is bad enough that we have done this for asprintf and vasprintf but they aren't part of the spec which is why he allows a specific check for them.
Essentially the only way to fix it is to use functions. On Fri, Jan 30, 2015 at 10:20 AM, Jacek Caban wrote: On 01/30/15 06:00, Martell Malone wrote: Correct Seems like the patch works as I intended:) I will do a patch to turn them back to functions without inline and hopefully this puts all the issues to rest:) This will bring back previous problems again. I don't see how using POSIXCSOURCE would change it. Also, you still have an issue about time32t vs time64t. How about the attached patch? It ensures that POSIXTHREADSAFEFUNCTIONS is defined if we declare.r functions.
This conforms POSIX better and you may simply detect those functions in the code using this macro. You said on IRC that all those changes are needed because VLC maintainer wants mingw-w64 to be POSIX compatible, would that make him happy? CheersJacek - Dive into the World of Parallel Programming. The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@. Thanks, Kai 2015-01-30 11:45 GMT+01:00 Jacek Caban: All those functions are emulated anyway.
- mingw-w64-headers/crt/io.h 8 - mingw-w64-headers/crt/secapi/ios.h 33 - 2 files changed, 6 insertions(+), 35 deletions(-) delete mode 100644 mingw-w64-headers/crt/secapi/ios.h - Dive into the World of Parallel Programming. The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more.
Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@. Attachments: Correct Seems like the patch works as I intended:) I will do a patch to turn them back to functions without inline and hopefully this puts all the issues to rest:) On Fri, Jan 30, 2015 at 12:57 AM, Erik van Pienbroek wrote: Martell Malone schreef op vr om 00:32 +0000: Is this with the patch I posted to the mailing list?
Correct - Dive into the World of Parallel Programming. The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@. Martell Malone schreef op do om 15:23 +0000: This change makes sense.
Right now Eric is checking this change on Fedora. So we should wait for his results. Yes but I think he should also build on rc1 without the patch to make sure that if there is a breakage this is the cause.
I'm currently doing a mass rebuild test run with mingw-w64 v4.0rc1 including the patch mentioned in this thread. It takes around 24hours to prepare and complete such a test mass rebuild. I wasn't really planning on also doing a test mass rebuild with plain v4.0rc1 (without the patch).
However, I do was planning to introduce GCC 5 in Fedora soon (the native gcc in Fedora was also just updated to the latest GCC 5 snapshot) and use this to do another test mass rebuild. Regards, Erik. Attachments: This change makes sense. Right now Eric is checking this change on Fedora. So we should wait for his results.
Yes but I think he should also build on rc1 without the patch to make sure that if there is a breakage this is the cause. Btw Martell, the fopens emulation-function would be something good IMO.
We should consider then emulation also for freopens, wfopenswfreopens, and freads. We might want the unlocked-version there too. Okay in that case I'll try to prepare a patch for that sometime next week. I want to get some dx11 changes and hopefully this inline issue fixed before 4.x so that has my full attention atm. On Thu, Jan 29, 2015 at 8:04 AM, Kai Tietz wrote: This change makes sense. Right now Eric is checking this change on Fedora. So we should wait for his results.
This might be something we would like to back-merge later to the 4.x branch. Btw Martell, the fopens emulation-function would be something good IMO. We should consider then emulation also for freopens, wfopenswfreopens, and freads.
We might want the unlocked-version there too. Kai 2015-01-28 22:00 GMT+01:00 Martell Malone: This should fix the issue of windows programs assuming localtimer and gmtimer unavailable. if POSIXCSOURCE is defined then we are specifically asking for them.
Quote from 'A POSIX-conforming application should ensure that the feature test macro POSIXCSOURCE is defined before inclusion of any header.' Any posix application that does not do this needs to be patched todo this and not mingw-w64 to accommodate them - Dive into the World of Parallel Programming.
The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@. - Dive into the World of Parallel Programming. The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@.
This change makes sense. Right now Eric is checking this change on Fedora. So we should wait for his results. This might be something we would like to back-merge later to the 4.x branch. Btw Martell, the fopens emulation-function would be something good IMO. We should consider then emulation also for freopens, wfopens, wfreopens, and freads. We might want the unlocked-version there too.
Kai 2015-01-28 22:00 GMT+01:00 Martell Malone: This should fix the issue of windows programs assuming localtimer and gmtimer unavailable. if POSIXCSOURCE is defined then we are specifically asking for them. Quote from 'A POSIX-conforming application should ensure that the feature test macro POSIXCSOURCE is defined before inclusion of any header.' Any posix application that does not do this needs to be patched todo this and not mingw-w64 to accommodate them - Dive into the World of Parallel Programming.
The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@. Attachments: Hi Philip, I was following this issue on msys2.
Would the mariabd guys not allow fopen instead of fopens to be used in their source? I can create an emulated function for mingw-w64 for you but it's not up to me if it gets merged Kind Regards Martell On Wed, Jan 28, 2015 at 10:48 PM, Philip A Reimer wrote: Would someone be able to add fopens to mingw? I am unable to use MariaDB Client Library on Windows XP I am currently using this patch as a workaround - Dive into the World of Parallel Programming.
The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@. This email is posted to several mailing-lists: win-builds', mingw-w64 and the caml-list.
Hi, I am happy to announce the availability of Win-builds 1.5.0 which is the result of many months of work in order to add new packages, update available ones and make all operations simpler and more intuitive. Homepage: Downloads: Documentation: Support information (IRC, MLs): Package list (informative): Source: Project Description Win-build is best described as a free software distribution for Windows: the goal isn't to provide dumps of binaries but to build something new, well-integrated, easy to install and upgrade, focused on stability (but without being out-of-date either), with a good package coverage and identical binaries on Windows and Linux.
New in 1.5.0 Complaints for the previous version centered around simplicity and package coverage. As such, this new version has focused on making it simpler to edit packages (modifying existing packages or adding new ones) and install thanks to more automated build steps on Linux and to the re-introduction of a GUI on Windows.
New Packages The package count has risen to 90. This may seem low compared to Linux distributions but this is enough to build GUI applications using either the EFLs, Qt and GTK+ (and many more). This makes a lot of sense if you consider how many packages on Linux make little sense on Windows: smartd, pciutils, all the X-related ones, KDE and Gnome, motif, mt.
GUI Package Manager and Installer on Windows The GUI is written using ocaml-efl and is used as the installer on Windows. The actual executable relies on several dozens of files (libraries and resources) and is packed into a self-extracting (and cleaning) executable to make it appear as a single file that can be readily run1. Its build is not documented for this release as a sign that the ocaml cross-compiler has some quirks2. Getting full and upstream support for cross-compilation is however something I'll be working on from now on. More Scripted Installation on Linux On the developer side, the component that runs all the build scripts has been rewritten from shell script to OCaml.
This provides a simple validity check of the build list description and proper ordering of the build steps, making it safer for people to do their own edits. To honor the great tradition of OCaml programs taking advantage of high-level optimizations, doesn't attempt to build several packages in parallel for a given architecture. It however builds for two architectures in parallel, thereby providing a reasonable efficiency.
Documentation Documentation has been updated and expanded. It finally properly covers the topic of creating new packages and is therefore now fairly exhaustive when it comes to the win-builds project. Over the next few days, the documentation will be expanded again to cover more topics related to usage on Windows, in particular with IDEs. Post-mortem and Future This release took much longer than planned. Roughly twice as long. This is due to two factor: adding the GUI for the package manager and installer which was planned for the subsequent version, and Qt. The GUI seems to have been worth it with much better download stats and close to a hundred installations per day (more than +40%), without additional publicity.
these numbers are guaranteed and not inflated by anything Qt will be dealt with in a dedicated section below. -next repository The work leading to this version, as is most often the case, has made apparent a number of issues with the development process. The main issue is probably the time it takes between the addition of a feature request and the availability of the corresponding package. This has little to do with the actual packaging or updating work and almost everything to do with the lack of a repository for the next version. As such, starting with the first changes after 1.5.0, there will be a '-next' version that will be regularly updated with packages built from the latest code and publicly reachable.
New contributions: what has been done and what's coming up A number of new contributors and contributions have appeared. Most changes were fairly late in the development cycle and have therefore not been merged in the main tree for 1.5.0. The code hosting has been moved to a gitolite in order to allow hosting of branches from others. This is for added convenience and any publicly-reachable git hosting is fine for merging back to the main branches.
Qt Some packages unfortunately require a lot of work with each new version. Actually the set of such packages has only one inhabitant: Qt. I'll be frank: maintaining a Qt that is cross-compiled from Linux for Windows is probably close to a full-time part-time job, i.e.
Something that will take all the time for someone doing part-time on it. My perception is probably flawed since I've made the initial packaging and it includes things that have probably never been done before and definitely deviate from what upstream had in mind (i.e. Cross-compile qmake itself). It is also unfortunately to be expected that each new version of Qt breaks something for this packaging (cross-compile to Windows). As such, additional maintainers are looked for. There is no reason to be afraid and this is not about abandoning the package unless someone steps up.
This is entirely in order to be able to better track upstream releases. Security Updates This part has mostly been a failure. The work involved was larger than expected and was let slip by without bound. Basically, the work (reading, updating the source, rebuilding, testing, uploading, announcing) is sometimes too much to do immediately after the availability of a security fix. With no strict bound and with the need to spend time on large changes in the build architecture, the updates have slipped by one day at a time.
As usual, Frederick P. Brooks got it right: Q: How does a large software project get to be one year late? A: One day at a time. The larger architecture have been done. There will be others but they should be less pervasive and shouldn't block working on other tasks for as much time.
More importantly, at least for this release, the official goal is to handle most security updates in 3 days at most and let none slip by more than 8 days. This should be at least as good as most large Linux distributions. Any security update lagging behind for more than that should be considered 'unnoticed' and a poke warranted. PS 1 It obviously takes some time to extract the 25MB or so (8MB compressed) but it is fast enough and can most probably be made faster.
The main advantage however is that this solves the issue of replacing files which are in-use: the package manager depends on.dll files and therefore would have been unable to ever replace these without resorting to complex tricks. 2 Perhaps the best proof is the following top-level code: let initcount = ref 0 let init = if!initcount = 0 then ( dotheactualinit ; incr initcount; ) else let = init On Windows I had to add an explicit call to the 'init' function from somewhere else in the code. Adrien Nader.
Attachments: 2015-01-25 6:13 GMT+03:00 Dongsheng Song: On Fri, Jan 23, 2015 at 6:35 PM, Jacek Caban wrote: On 01/22/15 15:35, Dongsheng Song wrote: Please review. Looks good to me.
ThanksJacek Pushed as 842d5c6b20526a78b3d29550c9dd196ec3215d21. Can you also do th same for 'fopens'? It also is missing on WinXP.
ThanksDongsheng - New Year. New Location.
New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. Mingw-w64-public mailing list Mingw-w64-public@.
Erik van Pienbroek schreef op ma om 21:29 +0100: JonY schreef op zo om 09:36 +0800: Hello allv4.x has been branched, and the first release candidate has been released on sourceforge. If all goes well, v4.0.0 will be released by next week.
Testers, please give it a spin! Thanks for the pre-release! I'm going to push it to Fedora rawhide and Fedora 21 testing. Afterwards another iteration of the test mass rebuild can be performed. Initial testing has shown that static libraries which were built against an older mingw-w64 trunk snapshot may need to be rebuilt. For example the static qt5-qtbase libraries in Fedora 21 and rawhide cannot be used any more as can be observed at This seems to be caused by the fact that packages like this were built against a mingw-w64 trunk snapshot where the symbol localtimer still was part of the mingw-w64-crt libraries. I guess this is an intentional change and the solution is to rebuild the affected packages against mingw-w64 v4.0rc1.
Regards, Erik van Pienbroek. Makefile changes looking good for me. Please go ahead and apply. Thanks, KAi 2015-01-26 13:00 GMT+01:00 Jacek Caban: - mingw-w64-crt/Makefile.am 13 mingw-w64-crt/libsrc/locationapi.c 5 2 files changed, 18 insertions(+) create mode 100644 mingw-w64-crt/libsrc/locationapi.c - Dive into the World of Parallel Programming.
The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@. Generated header is ok. Thanks, Kai 2015-01-26 13:00 GMT+01:00 Jacek Caban: - mingw-w64-headers/include/locationapi.idl 50 1 file changed, 50 insertions(+) - Dive into the World of Parallel Programming.
The Go Parallel Websitesponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. Mingw-w64-public mailing list Mingw-w64-public@.
The PCI Utilities What's that? The PCI Utilities are a collection of programs for inspecting and manipulating configuration of PCI devices, all based on a common portable library libpci which offers access to the PCI configuration space on a variety of operating systems. The utilities include: (See their manual pages for more details) lspci displays detailed information about all PCI buses and devices in the system setpci allows reading from and writing to PCI device configuration registers. For example, you can adjust the latency timers with it. Supported systems The library (and therefore all the utilities) works on the following operating systems:. Linux. FreeBSD.
NetBSD. OpenBSD. GNU/kFreeBSD. Solaris/i386.
AIX. GNU Hurd. Windows. CYGWIN.
BeOS. Haiku. Darwin However, not everything is supported on all systems. Some back-ends are read-only, some access the I/O ports directly, which need not work reliably. The only back-end which has all the features is Linux with a recent kernel. In particular, the port to Windows is obsolete and it currently lacks a maintainer.
If you are willing to step up and fix the issues, please let us know. Download The latest release of pciutils is version 3.6.2 (2018-08-12). You can download it from the following servers.
Please note that we provide only sources, not compiled binaries for any system. (the master site). (expect a few hours delay) Sometimes, development versions are also avaiable for testing. If you feel brave, download them from the alpha directory of the FTP servers.
There is also a public tree at containing the current development code. You can also view the of the development tree. The Git tree is mirrorred at. PCI IDs The PCI Utilities also contain a list of known vendors and devices. It is used for displaying vendor/device names instead of the ID numbers reported by the devices themselves.
The list is maintained separately by the project. Daily snapshots are available there and also mirrored at. If lspci doesn't recognize some device in your machine and you know what the device is, please to the database. Feedback You can ask questions and report bugs on the linux-pci mailing list running on, but please Cc the author ( [email protected]). Announcements about new versions are also sent to the list.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |