пт, 3 февр. 2023 г., 02:46 Phyllis Smith <phylsmith2017@gmail.com>:
In testing the 0001-noexecstack...patch, dmesg did not have the following message anymore:
    process '/cinelerra-5.1-build/bin/cin' started with executable stack
But now I have the message:
   asus 0003:0B05:1837.0004: Unmapped Asus vendor usagepage code 0xec

I tried web-search and this specific message seems to be related to fancy keyboard?


https://gitlab.com/asus-linux/asusctl/-/issues/43

so may be it was unrelated to my patch ...



Soooooo, I just do not know if this patch is a good solution or will create unknown problems.  Without more knowledge, it is probably best to leave it out for now unless someone knows for sure that it is a better idea.

On Thu, Jan 26, 2023 at 4:50 PM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:


пт, 27 янв. 2023 г., 02:49 Andrew Randrianasulu <randrianasulu@gmail.com>:
this one

чт, 12 янв. 2023 г., 06:58 Andrew Randrianasulu <randrianasulu@gmail.com>:


чт, 12 янв. 2023 г., 06:21 Rob Prowel <rprowel@comcast.net>:
On 1/11/23 07:37, Andrew Randrianasulu wrote:
> ср, 11 янв. 2023 г., 13:30 Andrew Randrianasulu <randrianasulu@gmail.com>:
>
> can you check if something like attached patch fixes it for you?
>
> i hope it was only o file with missing GNU.stack
> note, old linkers may dislike this and also it seems clang linker (lld)
> default on termux does this by default ....

re -- patch

-LDFLAGS1 = -Wl,-export-dynamic -g
+LDFLAGS1 = -Wl,-export-dynamic -g -Wl,-z,noexecstack

Are you sure you want to do this?  Is is portable?


I'll try to check on few systems where cingg builds - FreeBSD, NetBSD, various linux from ubuntu to Rosa to Slackware (we do not build on Irix, Solaris, HP-UX .... And cygwin  probably uses gnu binutils?)


I asked more if patch was working for you in this case ...even if it turned to be unportable we can selectively apply it....

Might an alternate solution have merit? ie scanning the blob resources
and saving their hex data as static arrays and then compiling and
linking the resulting .o files, which presumable only contain .data
segments?  Increases build time and complexity but seems more portable.


thanks for idea .... I think pngtoh tool in guicast tries to do that. (turns png into data arrays inside header)