Hi
I have a working branch that I managed to shrink bsp_specs to
being empty on some targets. It would be nice if we could
do this from the beginning on x86_64.
Are the options triggered by -qrtems really needed or implied
already?
For the BSPs I worked through, it was easy to move the start
fil
The original commit in GCC's repo is here:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=ab55f7db3694293e4799d58f7e1a556c0eae863a
We need this to be able to use crti.o and crtn.o in the bsp_specs file for the
port, and therefore provide missing symbols like "_fini" which RTEMS assumes are
defi
On 08/05/18 11:50, Chris Johns wrote:
On 8/5/18 7:18 pm, Sebastian Huber wrote:
This CFLAGS is not set before line 3071 in the script. The caller must have
provided it. I don't know how the caller did achieve this and why.
Is it ...
CFLAGS="-Wxx -Wyyy -Os" ../rtems/configure ...
?
This
On 8/5/18 7:18 pm, Sebastian Huber wrote:
>
> This CFLAGS is not set before line 3071 in the script. The caller must have
> provided it. I don't know how the caller did achieve this and why.
>
Is it ...
CFLAGS="-Wxx -Wyyy -Os" ../rtems/configure ...
?
Chris
_
On 08/05/18 11:10, Chris Johns wrote:
On 8/5/18 5:17 pm, Sebastian Huber wrote:
This change adds the warning flags. I don't know why CFLAGS is now present.
What do you mean by this last sentence?
We have:
grep '\' -n c/src/configure
640:CFLAGS
759:CFLAGS
1332:To assign environment variables
On 8/5/18 5:17 pm, Sebastian Huber wrote:
> This change adds the warning flags. I don't know why CFLAGS is now present.
What do you mean by this last sentence?
> There could be a problem somewhere else.
The support was added back in 2011 )d71462b4eb38efbcda6d429a0a61749d7a89e195).
I moved this:
This change adds the warning flags. I don't know why CFLAGS is now
present. There could be a problem somewhere else.
diff --git a/c/src/configure.ac b/c/src/configure.ac
index f4428ed221..7e4986e03d 100644
--- a/c/src/configure.ac
+++ b/c/src/configure.ac
@@ -100,7 +100,7 @@ RTEMS_PROG_CCAS
RTE
