Re: "signal()" in RTEMS unresolved

2023-08-22 Thread Joel Sherrill
t; *Sent:* Tuesday, August 22, 2023 4:14 PM > *To:* Brett Sterling > *Cc:* users@rtems.org > *Subject:* Re: "signal()" in RTEMS unresolved > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the

Re: "signal()" in RTEMS unresolved

2023-08-22 Thread Brett Sterling
Cc: users@rtems.org Subject: Re: "signal()" in RTEMS unresolved CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On Tue, Aug 22, 2023 at 4:46 PM Brett Sterling

Re: "signal()" in RTEMS unresolved

2023-08-22 Thread Joel Sherrill
On Tue, Aug 22, 2023 at 4:46 PM Brett Sterling wrote: > Hello all, > > My code calls the 'signal()' function. There are no errors during > compile, but when it goes to the link stage, it gets an error: > > : in function `Encore::Framework::Component::Component(unsigned int, > double)': >

"signal()" in RTEMS unresolved

2023-08-22 Thread Brett Sterling
Hello all, My code calls the 'signal()' function. There are no errors during compile, but when it goes to the link stage, it gets an error: : in function `Encore::Framework::Component::Component(unsigned int, double)': Component.cpp:(.text+0x1338): undefined reference to `signal' I've seen