Date: Sun, 12 Oct 2014 16:26:33 -0400 From: Naram Qashat <cyberbotx@cyberbotx.com> To: freebsd-ports@FreeBSD.org Cc: rene@FreeBSD.org Subject: Fwd: Re: devel/mingw32-gcc problem Message-ID: <543AE3F9.7080501@cyberbotx.com> In-Reply-To: <2B0375AF-1377-4E2F-A08D-CE44698B68D9@FreeBSD.org> References: <2B0375AF-1377-4E2F-A08D-CE44698B68D9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- Forwarded Message -------- Subject: Re: devel/mingw32-gcc problem From: David Chisnall <theraven@FreeBSD.org> Date: Sun, 12 Oct 2014 21:07:03 +0100 Cc: freebsd-toolchain@FreeBSD.org, rene@FreeBSD.org There have been some changes to how the ports tree handles libtool files recently, but I don't know the details. You'd be better off asking on the ports list or in #bsdports on EFNet. David On 10 Oct 2014, at 21:36, Naram Qashat <cyberbotx@cyberbotx.com> wrote: > Hi everyone, > > I've been trying to push out an update to devel/mingw32-gcc, but ran into a problem, and Rene suggested asking about it here. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191291 > > Long story short, some of the .a files installed by devel/mingw32-bin-msvcrt get clobbered (their contents becomes nothing but NUL bytes) during the build of mingw32-gcc. This only happens under 10.x and not under 9.x or earlier. > > I'm not subscribed to this mailing list, so please CC me on any replies. > > Thanks, > Naram Qashat I'm forwarding this message as suggested by David. I'm not sure if the libtool changes would account for the problem I'm running in to, as the files being clobbered are archives and not libtool files. But if anyone has any insight about this, I'd really appreciate it, as I would like to update the port and this has been a major stopping point. Thanks, Naram Qashat
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?543AE3F9.7080501>