On Mon, Jan 06, 2025 at 10:03:50AM -0700, Jeff Law wrote:
>
>
> On 1/6/25 10:02 AM, Stafford Horne wrote:
> > On Mon, Jan 06, 2025 at 07:37:56AM -0700, Jeff Law wrote:
> > >
> > >
> > > On 1/6/25 6:01 AM, Stafford Horne wrote:
> > > > In the OpenRISC build we get the following warning:
> > > >
On 1/6/25 10:02 AM, Stafford Horne wrote:
On Mon, Jan 06, 2025 at 07:37:56AM -0700, Jeff Law wrote:
On 1/6/25 6:01 AM, Stafford Horne wrote:
In the OpenRISC build we get the following warning:
ld: warning: __modsi3_s.o: missing .note.GNU-stack section implies
executable stack
On Mon, Jan 06, 2025 at 07:37:56AM -0700, Jeff Law wrote:
>
>
> On 1/6/25 6:01 AM, Stafford Horne wrote:
> > In the OpenRISC build we get the following warning:
> >
> > ld: warning: __modsi3_s.o: missing .note.GNU-stack section implies
> > executable stack
> > ld: NOTE: This behaviour
On 1/6/25 6:01 AM, Stafford Horne wrote:
In the OpenRISC build we get the following warning:
ld: warning: __modsi3_s.o: missing .note.GNU-stack section implies
executable stack
ld: NOTE: This behaviour is deprecated and will be removed in a future
version of the linker
Fix this b
In the OpenRISC build we get the following warning:
ld: warning: __modsi3_s.o: missing .note.GNU-stack section implies
executable stack
ld: NOTE: This behaviour is deprecated and will be removed in a future
version of the linker
Fix this by adding a .note.GNU-stack to indicate the stack