As you seem to be around now, could we do a call to try and get this fixed? Are you on the rsync discord server? https://discord.gg/zHzPNc6R if you can't do discord, then zoom?
On Thu, 16 Jan 2025 at 06:18, <rsbec...@nexbridge.com> wrote: > Also, the patch I previously sent works correctly on x86, but not ia64. > This problem is isolated to popt/findme > > > > *From:* rsync.project <rsync.proj...@gmail.com> > *Sent:* January 15, 2025 2:11 PM > *To:* rsbec...@nexbridge.com > *Cc:* Perry Hutchison <pl...@agora.rdrop.com>; rsync@lists.samba.org > *Subject:* Re: new release 3.4.0 - critical security release > > > > Is there a way I can get access to a machine 3.4.0 is failing to build on? > Maybe a VM under VirtualBox? Or some cloud service? > > I don't have an ia64 > > > > On Thu, 16 Jan 2025 at 01:20, <rsbec...@nexbridge.com> wrote: > > On January 14, 2025 11:20 PM, Perry Hutchison wrote: > >"Randall S. Becker via rsync" <rsync@lists.samba.org> wrote: > > > >> FYI: I think this is just missing #include "rsync.h" in popt/findme.c > > > >Structurally, this seems very odd. I thought popt was a generic argument > handler, > >which should not need to #include details of the application that is using > it. > > I thought so too, but it is now pulling in things from util2 and other > areas > needing rsync.h and ifuncs.h. > I still have not managed to get it to link correctly on ia64 and am > seriously considering giving up. > >
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
