Which is not available on most architectures.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1377#issuecomment-1332141570
You are receiving this because you are subscribed to this thread.
Message ID: ___
To be clear: luajit maintenance is not doing well - it was abandoned, forked,
then the maintenance of the original resumed but patches from the fork have not
been merged back. The JIT works on x86, Arm, and ppc32 but pretty much nothing
else. Specifically s390 and ppc64 was implemented at some p
lua5.1 -l 'foobar'
lua5.1: module 'foobar' not found:
no field package.preload['foobar']
no file './foobar.lua'
no file '/usr/local/share/lua/5.1/foobar.lua'
no file '/usr/local/share/lua/5.1/foobar/init.lua'
no file '/usr/local/lib/lua/5.1/foobar.lua'
What 'stuff' would conflict, specifically?
Why does it not conflict when it's written in C but it does conflict when
written in Lua?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2309#issuecomment-1332168380
You are receiving this be
What is 'average lua interpreter'?
It's based on liblua, it's the same interpreter as any other.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2309#issuecomment-1332182236
You are receiving this because you are subscribed to this thr
Sorry, I don't get what the problem is.
You can explicitly load a lua module, and then it will be searched in the load
path.
If you exclude the standard search path it means that already installed lua
libraries cannot be explicitly loaded when lua code is running in rpm. That
sounds like a bug
How would the rpm process crash?
It requires that a user script loads a library, it cannot crash based on the
sole existence of a library.
The load path can be altered from the script anyway, it's just tedious.
Meaning that this does not in practice prevent use of libraries, only makes the
use
And what use is lua exactly if you cannot load any libraries?
The language is designed for embedding and is very simplistic which means that
it relies on libraries for pretty much anything.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issu
Also it's bad design on RPM's part that when rpm crashes the whole transaction
is lost.
Have you ever heard of power outage?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2309#issuecomment-1332225748
You are receiving this because yo
I want to use lua in a rpm spec file.
lua provides very limited capabilities out of the box so I need libraries to do
pretty much anything.
With this limited search path I cannot use libraries that are already provided
by the system.
--
Reply to this email directly or view it on GitHub:
https
For one I would like to have the Lua inspect library available.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2309#issuecomment-1332291462
You are receiving this because you are subscribed to this thread.
Message ID: _
The problem is more general, though.
Lua in itself provides very little functionality without any libraries.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2309#issuecomment-1332293665
You are receiving this because you are subscribed
Like rpm.execute is 4.15+ so I cannot rely on that, need a library.
Capturing the output is not supported at all, need a library.
The lua standard library handles execution by shell but not quoting of
arguments (for security of rpm !!!), need a library.
--
Reply to this email directly or view
Right, you can cut & paste the library. And then there is a bug and you need to
update all your spec files. Scales really well.
The execute is not there forever:
```
execute(path [, arg1 [,…])
Execute an external command (rpm >= 4.15.0) This is handy for executing
external helper commands witho
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
%if 1 && ( 2 ||
3 )
%endif
error: unmatched (
error: /home/michal/kernel-source/test.spec:1: bad %if condition
%if 1 && ( 2 || \
3 )
%endif
error: parse error in expression
error: unmatched (
error: /home/michal/kernel-source/test.spec:2: bad %if condition
%if 1
There should be only one \ but github does not display it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/775#issuecomment-506706175__
Thanks for the fix. The 4.14.2.1 version I use does not use the lineType
classification. I suppose this will be fixed in 4.15. Due to non-trivial amount
of custom macros upgrading is going to take a while.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
Thanks for the fix. The 4.14.2.1 version I use does not use the lineType
classification. I suppose this will be fixed in 4.15. Due to non-trivial amount
of custom macros upgrading is going to take a while.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
hramrach left a comment (rpm-software-management/rpm#3746)
It works with -DCMAKE_CXX_COMPILER=g++-13 but not -DCMAKE_CXX_COMPILER=gcc-13
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3746#issuecomment-2853766984
You are receiving this
hramrach left a comment (rpm-software-management/rpm#3746)
It's not great UX that the gcc binary does not support compiling C++ but
instead of rejecting the file it miscompiles it. Is it perhaps possible to
detect the miscompilation?
--
Reply to this email directly or view it on GitHub:
https:
Fixes: rpm-software-management/rpm#3746
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/3747
-- Commit Summary --
* INSTALL: Add C++ 20 requirement
-- File Changes --
M INSTALL (9)
-- Patch Links --
https://github.co
@hramrach pushed 1 commit.
354d6a4cdbdc6ce44d4b8c5a8f2d3a6aac9da525 INSTALL: Add C++ 20 requirement
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3747/files/b8bc999303c357363711ddfad94cacfd5b2e1a9a..354d6a4cdbdc6ce44d4b8c5a8f2d3a6aac9da525
You are receiving this beca
hramrach created an issue (rpm-software-management/rpm#3746)
**Describe the bug**
fails to build
**To Reproduce**
Steps to reproduce the behavior:
1. git clone https://github.com/rpm-software-management/rpm.git
2. mkdir rpm/bin
3. cd rpm/bin
4. cmake -DCMAKE_CXX_COMPILER=gcc-13 ..
5. make
*
24 matches
Mail list logo
