On 03/10/2016 04:54 PM, Jens Rehsack wrote:
Am 10.03.2016 um 06:13 schrieb Gary Thomas :
I'm working on a package (amanda - the Advanced Maryland Archiving
system) that is written heavily in perl with swig interfaces to C.
This code ran great until the update to perl 5.22; it now dies a
horrib
Compare the output of configure run on working and non working versions.
Usually this is very helpful. See if its enabling or disabling something
new.
On Mar 10, 2016 10:55 PM, "Jens Rehsack" wrote:
>
> > Am 10.03.2016 um 06:13 schrieb Gary Thomas :
> >
> > I'm working on a package (amanda - the
As another point of information, I'm having similar issue with perl
5.22.1 on some arm boxes (native Gentoo builds) and even some odd
build differences between amd box and intel corei5 9 (I know,
weird...).
The issue I'm hitting is basically a horribly broken upstream
Configure script, and in my c
On 2016-03-10 16:54, Jens Rehsack wrote:
Am 10.03.2016 um 06:13 schrieb Gary Thomas :
I'm working on a package (amanda - the Advanced Maryland Archiving
system) that is written heavily in perl with swig interfaces to C.
This code ran great until the update to perl 5.22; it now dies a
horrible
> Am 10.03.2016 um 06:13 schrieb Gary Thomas :
>
> I'm working on a package (amanda - the Advanced Maryland Archiving
> system) that is written heavily in perl with swig interfaces to C.
> This code ran great until the update to perl 5.22; it now dies a
> horrible death on almost every activity.
I'm working on a package (amanda - the Advanced Maryland Archiving
system) that is written heavily in perl with swig interfaces to C.
This code ran great until the update to perl 5.22; it now dies a
horrible death on almost every activity. These failures seem to
always be in the swig generated wr
