Re: Any routine way to switch from x86_64 to i386?
> 在 2020年4月11日，下午8:02，Ryan Schmidt 写道： > > On Apr 11, 2020, at 06:45, Xim wrote: > >> I am doing some port test on a Snow Leopard system. At first and by default, >> I installed some dependencies with x86_64 arch. I realized the problem, >> changed the build arch option in macports.conf. But the port system seems a >> little unstable at dealing with this kind of issue. New dependencies come >> out again and again during the installing process. I am currently trying >> uninstalling and reinstall all (i386) ports. I wonder if there is a routine >> way of dealing with an arch switch? > > If you change build_arch in macports.conf you should probably uninstall and > reinstall all ports that are not identified by "port -v installed" as noarch. > > A possible alternative is to install ports with the +universal variant. Then > you'll get both x86_64 and i386 at the same time. You can use the "arch" > program if you need to try running the 32-bit part of a universal binary on a > 64-bit computer. Thanks for your reply! The reinstall solution works for me. In addition, for others’ information, some cleaning may need to be done for previously installed ports. Regards, Xim chenguoka...@mails.ucas.ac.cn
Any routine way to switch from x86_64 to i386?
Dear developers, I am doing some port test on a Snow Leopard system. At first and by default, I installed some dependencies with x86_64 arch. I realized the problem, changed the build arch option in macports.conf. But the port system seems a little unstable at dealing with this kind of issue. New dependencies come out again and again during the installing process. I am currently trying uninstalling and reinstall all (i386) ports. I wonder if there is a routine way of dealing with an arch switch? Regards, Xim chenguoka...@mails.ucas.ac.cn
A currently unstable CI?
Dear developers, About an hour ago I submitted a modified commit which only contains a typo fix in the note. To my surprise, Travis Build failed for two times, both reported that one of my dependencies failed. I checked the two logs. https://travis-ci.org/macports/macports-ports/builds/670449019 and https://travis-ci.org/macports/macports-ports/builds/670450648 Both of them failed with dependency affairs. The difference is where the build fails. My Portfile does not explicitly specify any extra dependencies so I suspect the stability of the builder. Any actions may I take? Regards, Xim chenguoka...@mails.ucas.ac.cn
Re: Is there a way to test ports on snow leopard
> 在 2020年3月29日，下午3:09，Joshua Root 写道： > > On 2020-3-29 17:17 , Xim wrote: >> Dear Macport Developers, >> >> As the maintainer of stlink, I received a build failure message from the >> build bot, saying the port failed to build on snow leopard >> (https://build.macports.org/builders/ports-10.6_i386-watcher/builds/4691). >> I checked the log and identified the cause of build failure. Since I do >> not own a snow leopard machine, I wonder if there is a way for me to >> test a patch. By the way, builders of GitHub Pull Requests test only a >> few recent versions and some are marked to be allowed failures. May the >> build failure on snow leopard be tolerated ? >> >> >> Regards, >> Xim >> chenguoka...@mails.ucas.ac.cn <mailto:chenguoka...@mails.ucas.ac.cn> > > Maintainers are only expected to keep their ports working on the latest > 3 major releases of macOS, which right now means 10.13 and later. Older > versions may be supported at the maintainer's discretion, but users > should not be surprised if there are problems. Some users may submit > fixes for old systems, and it's nice to merge those if reasonable. > > We don't have any form of remote access to build machines for testing, > if that's what you're asking. You would need to get someone with a 10.6 > system to give you access, or set up a VM, if you want to do your own > testing. > > In this case though, it looks more like a bug affecting 32-bit systems > rather than anything directly to do with the OS version. I imagine you'd > likely be able to reproduce the problem on 10.13 with build_arch=i386. > > - Josh Thanks for your reply, I decide to inform the upstream that the problem still exists. (There was an issue which they thought solved). Waiting for new versions from upstream seems a proper solution. Regards, Xim chenguoka...@mails.ucas.ac.cn
Is there a way to test ports on snow leopard
Dear Macport Developers, As the maintainer of stlink, I received a build failure message from the build bot, saying the port failed to build on snow leopard (https://build.macports.org/builders/ports-10.6_i386-watcher/builds/4691 <https://build.macports.org/builders/ports-10.6_i386-watcher/builds/4691>). I checked the log and identified the cause of build failure. Since I do not own a snow leopard machine, I wonder if there is a way for me to test a patch. By the way, builders of GitHub Pull Requests test only a few recent versions and some are marked to be allowed failures. May the build failure on snow leopard be tolerated ? Regards, Xim chenguoka...@mails.ucas.ac.cn
Re: Port mechanism explanation needed
> 在 2020年3月25日，上午3:53，Jackson Isaac 写道： > > Hi Xim, > > On Tue, Mar 24, 2020 at 5:33 PM 陈国凯 wrote: >> >> I found no maintainers for port stlink and I wanted to take it if possible. >> However, I am quite confused with the portfile mechanism of this port. >> >> After reading the wiki, I know that this portfile specifies a Github Repo >> from which the port system obtains source code. While there are two problems >> left for me. >> >> 1. I tried editing portfile locally, changing the version number but port >> would only try fetching the source code from mirrors of MacPorts, rather >> than fetching directly from Github upstream. Is there a way for me to test >> my modifications locally? And how does the mirroring mechanism work? If one >> changed the portfile configuration and merged changes into port tree, would >> the mirrors be synced automatically? > > To fetch the source code/release tarball from upstream instead of > mirrors, use the following command: > sudo port -v fetch --no-mirror > > Once the Portfile is updated and merged into master, the mirrors start > to pickup the latest Portfile (there might be delays involved before > all mirrors are up to date). > >> 2. I cannot figure out to whom the checksums belongs. I downloaded all 1.6.0 >> source code from Github release page while none of them matches the checksum >> specified in the portfile. How can I obtain the file with the expected >> checksum from Github (not from mirrors because I intend to make an upgrade >> afterwhile so that I should find a way to configure checksum) > > The checksum you see on Github release page might have been computed > using a different checksum algorithm. > > If you download and run the rmd160 and sha256 checksum on the package, > then you should get the same checksum as mentioned in the portfile. > To make this easy, when you update the Portfile you can run the > following command > > sudo port -v checksum > > This will automatically calculate the correct checksum for the package > downloaded from the upstream. > > Stay safe, > Jackson Isaac Hi Jackson, I have figured out where the file comes from with the guidance of Rainer. After that the checksum works well. Thanks for your reply with additional information. :) Regards, Xim chenguoka...@mails.ucas.ac.cn
