On 04/03/2015 04:16 PM, Freddie Chopin wrote:
On 04/03/2015 08:44 AM, Spooge wrote:
Thanks for the files! I updated it and it should handle groups now
-- the output looked reasonable and more or less matches the log you
gave me I think. If you do try it out, tell me if you hit any issues.
Hmm... it doesn't seem to work with this particular project. Most of
the messages are almost identical:
Konsole output
$ ./script.sh
Assembler messages:
Fatal error: can't create
../../output/source/synchronization/ConditionVariable.o: No such file
or directory
Assembler messages:
Fatal error: can't create ../../output/source/threads/ThreadBase.o:
No such file or directory
Assembler messages:
Fatal error: can't create
../../output/source/synchronization/Mutex.o: No such file or directory
Assembler messages:
Fatal error: can't create
../../output/source/synchronization/MutexControlBlock.o: No such file
or directory
Assembler messages:
Fatal error: can't create
../../output/source/synchronization/Semaphore.o: No such file or
directory
Assembler messages:
Fatal error: can't create
../../output/source/synchronization/SemaphoreTryWaitFunctor.o: No
such file or directory
Assembler messages:
Fatal error: can't create
../../../../output/source/architecture/ARM/ARMv7-M/ARMv7-M-startup.o:
No such file or director
y
By looking at the generated script (also attached) it seems that all
that it misses is generation of appropriate output folders. If I
create some of them manually, the output can be found there.
But the bigger problem is the order of commands - produced script has
linking in 3/5 of the length, followed by compilation of some other
files which are needed for linking...
Another good addition would be a header like this:
#! /usr/bin/env bash
set -e
set -x
set -o pipefail
Would it be possible to mark produced file as executable? I had to do
"chmod +x ..." myself.
Regards,
FCh
I really appreciate the feedback! I think I fixed all those issues, and
I set up an arm cross compiler (the binary AUR one) but the build failed
for me when linking distortos.elf:
/test/ConditionVariable/conditionVariableTestCases.o -o
./output/distortos.elf
output/test/Signals/signalsTestCases.o:(.rodata._ZN9distortos4test12_GLOBAL__N_1L28generationOperationsTestCaseE+0x0):
undefined reference to `vtable for
distortos::test::SignalsGenerationOperationsTestCase'
output/test/Signals/signalsTestCases.o:(.rodata._ZN9distortos4test12_GLOBAL__N_1L24queuedOperationsTestCaseE+0x0):
undefined reference to `vtable for
distortos::test::SignalsQueuedOperationsTestCase'
I think it's pretty close now though if not all the way there (hoping
it's just a compiler config/version issue).
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups "tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
