Cut a new release?
Hi. Since libtool latest release 3 years ago, some important problems have been patched. In particular, "-fuse-ld=…" is now propagated to the driver when linking. For example, it is not possible to build LLVM modules using libtool on Ubuntu LTS using only released packages. "llvm-config --cxxflags" outputs "… -fuse-ld=gold -Wl,--no-keep-files-mapped …", and only the linker option "--no-keep-files-mapped" is passed to the driver (g++/clang++) while "-fuse-gold=ld" is dropped, causing GNU ld to halt with an error because "--no-keep-files-mapped" is a gold-only option. This is a known problem which has been fixed in libtool repository in Feb. 2016 (f9970d99293faf908fdc153a653fa5781095fb7a), but no libtool release seems to have taken place since then. Would it be possible to cut a formal release? Sam ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: Cut a new release?
On Fri, 21 Sep 2018, Samuel Tardieu wrote: Would it be possible to cut a formal release? Libtool is in need of additional volunteers to serve as maintainers to help catch up on the backlog of patches/issues and prepare another release. Are you able to volunteer to be a libtool maintainer? Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: Cut a new release?
Le ven. 21 sept. 2018 à 15:09, Bob Friesenhahn a écrit : > On Fri, 21 Sep 2018, Samuel Tardieu wrote: > > > > Would it be possible to cut a formal release? > > Libtool is in need of additional volunteers to serve as maintainers to > help catch up on the backlog of patches/issues and prepare another > release. > My question was solely about tagging and cutting a new release from the current state of the repository so that patches contributed by volunteers and accepted in the repository already get a more widespread distribution. I understand how getting through QA for doing a new release can be time consuming (unless the current commits already went through an exhaustive enough CI run). Note that some distributions such as ArchLinux have been using the current git HEAD as their sanctioned libtool package. This should increase the confidence that the current git HEAD behaves better than the latest release. Sam ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: Cut a new release?
On Fri, 21 Sep 2018, Samuel Tardieu wrote: Libtool is in need of additional volunteers to serve as maintainers to help catch up on the backlog of patches/issues and prepare another release. My question was solely about tagging and cutting a new release from the current state of the repository so that patches contributed by volunteers and accepted in the repository already get a more widespread distribution. Volunteers with the necessary energy, time, and resources are necessary in order to perform this function. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ https://lists.gnu.org/mailman/listinfo/libtool
