It'd be really helpful if you can turn this into a minimal reproducer that we
could then include in the test-suite.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2324#issuecomment-1352690084
You are receiving this because you are subs
> > For backward-compatibility and to avoid surprises, default to building
> > x86_64 even on v2+ capable machines.
> > Tested by running rpm --eval %_target_cpu and using rpmbuild with various
> > BuildArch values on a x86_64_v3 host.
>
> Looks like my fix for the platform macros generation bro
See issue #2319
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2315#issuecomment-1352900998
You are receiving this because you are subscribed to this thread.
Message ID: ___
Rpm-maint mailing l
(Bottom line being: only use BuildArch for `BuildArch: noarch`. All other uses
are not tested and also not documented.)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2315#issuecomment-1352902953
You are receiving this because you are su
> > The missing BMI and BMI2 are included in git master with
> > https://sourceware.org/pipermail/libc-alpha/2022-October/142395.html
> > meanwhile. OSXSAVE was still missing, I sent a patch for that:
> > https://sourceware.org/pipermail/libc-alpha/2022-December/143936.html
> > Once that is merg
> See issue #2319
Perfect match - so indeed a mostly independent topic.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2315#issuecomment-1352967373
You are receiving this because you are subscribed to this thread.
Message ID: __
You still haven't explained what you're actually trying to do, "use lua" or
"use library x" doesn't explain anything at all.
What is the problem you are solving with these tools? Like said, rpm macros are
nothing but a fancy text pre-processor. Complicated programming doesn't really
belong ther
> You still haven't explained what you're actually trying to do, "use lua" or
> "use library x" doesn't explain anything at all.
>
> What is the problem you are solving with these tools? Like said, rpm macros
> are nothing but a fancy text pre-processor. Complicated programming doesn't
> really
There's the thing that complex macros don't belong to rpm spec files nor macro
files either because the syntax of these files is undefined.
It's not possible to tell what the files mean, not possible to parse them, not
possible to test them.
Then if the macros cannot be in the spec files nor ma
I did another test, pack the same files in directory1 twice, then extract them
to different directory, There is still a difference between the static library
file，only a few bytes was changed, i use %!xxd to convert binary to
hexadecimal，here are the header of the two files, Indicate distinction
10 matches
Mail list logo
