RE: [taste-users] Failing TASTE Build

Hi Thanassis,

You are absolute right! The problem was related to the fact that I use GNAT-GPS for developing the manual code (thus compiling it once in a while).

I have now updated my GPS project files so that object files and other binaries are placed in a directory far, far away in the file system.

Thanks for your excellent help,

Gert

Gert Caspersen
Senior Engineer, Project Manager
Space Projects (DK)
Terma A/S

From: Thanassis Tsiodras [mailto:ttsiodras@xxxxxxxxxxx]
Sent: 26 April 2012 11:56
To: Gert Caspersen
Cc: taste-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [taste-users] Failing TASTE Build

Hi Gert - problem identified.

For some reason (manual compilation on your side?), your .zip files for the user code come with precompiled .o inside them.
These .o files are unziped inside the corresponding bin folders, and cause the "multiple definitions" link errors you are seeing.

To shield against this in the future, I will update the orchestrator to remove any .o files inside user-code-provided .zip files.
For your build to work, please remove these .o from the zip files of your user code.

Kind regards,
Thanassis.

--

------------------------------------------------------------

Thanassis Tsiodras, Dr.-Ing.

Semantix Information Technologies

email: ttsiodras@xxxxxxxxxxx

web  : http://www.semantix.gr

phone: (+30)2106412065

fax  : (+30)2106412068

addr.: K Tsaldari 62, 11476, Athens, GREECE

------------------------------------------------------------

On 25/4/2012 6:58 μμ, Gert Caspersen wrote:

Hi Maxime,

Thanks for the explanation. I have attached a tarball as you requested.

Regards,

Gert

Gert Caspersen
Senior Engineer, Project Manager
Space Projects (DK)
Terma A/S

From: Maxime Perrotin [mailto:Maxime.Perrotin@xxxxxxx]
Sent: 25 April 2012 15:42
To: taste-users@xxxxxxxxxxxxxxxxxxx; Gert Caspersen
Subject: Re: [taste-users] Failing TASTE Build

Yes, this is normal.

These package specifications correspond to the data models of your system.

You are using several ASN.1 modules:

Onboard-Monitoring DEFINITIONS ::=

Event-Reporting DEFINITIONS ::=

This is why in the dataview directory you have one .ads per ASN.1 module (one ASN.1 module => one Ada package)

The reason why you have a "duplicate" of the Ada packages of the data view in the directory "thechecktransitionreport" (and not in the others) is because you specified a functional state (or context parameter) in the interface view, for this block:

SYSTEM IMPLEMENTATION TheCheckTransitionReport.others
SUBCOMPONENTS
theReport_obj459 : DATA DataView::Check_Transition_Report
{ Taste::FS_Default_Value => "{}"; };

When you do that, it has the effect of generating a variable of the type that you chose in the model, and assign it the value you specified:

(file context_thechecktransitionreport.ads generated in the function root directory):

TYPE asn1SccContext_thechecktransitionreport IS RECORD
thereport : asn1SccCheck_Transition_Report;
END RECORD;

thechecktransitionreport_ctxt:aliased asn1SccContext_thechecktransitionreport:=(thereport => (Length=>0, Data="" others => (id => asn1Sccvoltage_1, value => (kind => type_1_0_PRESENT, type_1_0 => 0), limit_crossed => (kind => type_1_0_PRESENT, type_1_0 => 0), previous_checking_status => asn1Sccwitin_limits, current_checking_status => asn1Sccwitin_limits, transition_time => (p_field => (coarse_time_rep => 0, fine_time_rep => 0), coarse_time => (Data="" fine_time => (Data="">

This file is created together with the files it depends on in the function 'root' directory, i.e. the other dataviews.ads files. Note that the 'dataview' directory is not always generated, for example if your function had no interface using any data type. This is why it is necessary to have these files here.

Anyway, this is not causing the error you experience, since on my side I can build the system without any error.

Please send a tarball of your working directory, in the state where it is when you reach the error.

Maxime

On Wed, 25 Apr 2012 14:59:46 +0200, Gert Caspersen <gec@xxxxxxxxx> wrote:

                Hi Maxime,

OK, I have tried to purge the binary directory without any effect.

I have however discovered something fishy. It appears that some directories containing skeletons contains duplicates of the Ada package specifications inherited through the data view. Example from thechecktransitionreport function:

assert@assertvm:~/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/thechecktransitionreport$ ls -1r *

thechecktransitionreport.ads

thechecktransitionreport.adb

telecommand_verification.ads

standard_datatypes.ads

service_reports.ads

onboard_parameters.ads

onboard_monitoring_dataview.ads

onboard_monitoring.ads

event_reporting.ads

event_action.ads

context_thechecktransitionreport.ads

application_processes.ads

adaasn1rtl.ads

dataview:

telecommand_verification.ads

standard_datatypes.ads

service_reports.ads

onboard_parameters.ads

onboard_monitoring_dataview.ads

onboard_monitoring.ads

event_reporting.ads

event_action.ads

application_processes.ads

adaasn1rtl.ads

I have no idea as to how these duplicates have been created. My question now is: Should these package specifications be located in the ‘dataview’ subdirectory or in the ‘root’ directory?

                Thanks for helping,

                                Gert

Gert Caspersen
Senior Engineer, Project Manager
Space Projects (DK)
Terma A/S

From: Maxime Perrotin [mailto:Maxime.Perrotin@xxxxxxx]
Sent: 25 April 2012 14:33
To: taste-users@xxxxxxxxxxxxxxxxxxx; Gert Caspersen
Subject: Re: [taste-users] Failing TASTE Build

Hi Gert,

I tried to build the system using the Interface, Deployment and Data views that you sent previously and the build went fine. Here is what I did:

1) I renamed the dataview-uniq.asn that you sent to DataView.asn

2) I ran taste-edit-data-view, saved the file and closed it to get the updated DataView.aadl

3) I fixed the reference to TASTE-Directives.aadl in the interface view (as you did)

4) I ran taste-generate-skeletons

5) I ran build-script.sh

It ended with no error to the generation of a binary:

/home/maxime/taste/terma/binary/binaries/globalpartition_obj102

Did you do anything else?

I recommend that if you ran the build-script several times you try to remove the 'binary' directory first - some old Ada files may be remaining from a previous build, and if you changed some names in the interface view, this could lead to link errors.

Maxime

On Wed, 25 Apr 2012 13:44:34 +0200, Gert Caspersen <gec@xxxxxxxxx> wrote:
                Hi Thanassis,

Well, I have now encountered the next problem. When building the application using ‘build-script.sh’, it fails late in the link phase with the following error messages:

...

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/GlueAndBuild/deploymentview_final/globalpartition_obj102/associatedcheckstates.o: In function `associatedcheckstates_PI_UpdateCheckState':

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/associatedcheckstates/associatedcheckstates/associatedcheckstates.adb:49: multiple definition of `associatedcheckstates_PI_UpdateCheckState'

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/associatedcheckdefinitions/associatedcheckdefinitions/associatedcheckstates.o:associatedcheckstates.adb:(.text+0xf1): first defined here

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/GlueAndBuild/deploymentview_final/globalpartition_obj102/associatedcheckstates.o: In function `associatedcheckstates_PI_GetCheckState':

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/associatedcheckstates/associatedcheckstates/associatedcheckstates.adb:59: multiple definition of `associatedcheckstates_PI_GetCheckState'

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/associatedcheckdefinitions/associatedcheckdefinitions/associatedcheckstates.o:associatedcheckstates.adb:(.text+0xf9): first defined here

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/GlueAndBuild/deploymentview_final/globalpartition_obj102/parameterpool.o:(.data+0x0): multiple definition of `parameterpool_E'

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/parameterpool/parameterpool/parameterpool.o:(.data+0x0): first defined here

/home/assert/mbcode/Prototype/Design_Defin

gnatlink: error when calling /usr/bin/gcc-4.4

ition_File/Taste_Model/Onboard_Monitoring/binary/GlueAndBuild/deploymentview_final/globalpartition_obj102/parameterpool.o: In function `parameterpool_PI_getParameter':

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/parameterpool/parameterpool/parameterpool.adb:18: multiple definition of `parameterpool_PI_getParameter'

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/parameterpool/parameterpool/parameterpool.o:parameterpool.adb:(.text+0x0): first defined here

collect2: ld returned 1 exit status

gnatmake: *** link failed.

make: *** [all] Error 4

File "/opt/ocarina-2.0w-suite-x86-linux-2010.svn/bin/assert-builder-ocarina.py", line 2253, in <module>

    main()

File "/opt/ocarina-2.0w-suite-x86-linux-2010.svn/bin/assert-builder-ocarina.py", line 2246, in main

    bDebug, bUseEmptyInitializers, bCoverage)

File "/opt/ocarina-2.0w-suite-x86-linux-2010.svn/bin/assert-builder-ocarina.py", line 1092, in InvokeOcarinaMakefiles

    mysystem((cmd % customFlags) + extra + externals+"\" make")

File "/opt/ocarina-2.0w-suite-x86-linux-2010.svn/bin/assert-builder-ocarina.py", line 125, in mysystem

    traceback.print_stack()

Failed while executing:

cd './deploymentview_final/globalpartition_obj102' && ADA_INCLUDE_PATH="/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/applicationprocess/applicationprocess:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/thechecktransitionreport/thechecktransitionreport:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/associatedcheckstates/associatedcheckstates:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/reportedcheckstatetransitions/reportedcheckstatetransitions:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/thegenerator/thegenerator:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/checkedparameters/checkedparameters:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/thechecker/thechecker:/home/assert/mbcode/Prototype/Design_Defini tion_Fi le/Taste_Model/Onboard_Monitoring/binary/associatedcheckdefinitions/associatedcheckdefinitions:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/missiondatabase/missiondatabase:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/parameterpool/parameterpool:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/ground/ground:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/Backdoor:/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/vt_checkedparameters_configure" USER_CFLAGS="${USER_CFLAGS} -m32 " USER_LDFLAGS="${USER_LDFLAGS} -m32 -lm " EXTERNAL_OBJECTS="-lrt /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/auto-src_PLATFORM_LINUX32/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/thechecker/thechecker/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/associatedcheckstates/associatedcheckstates/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/associatedcheckdefinitions/associatedcheckdefinitions/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/thegenerator/thegenerator/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/thechecktransitionreport/thechecktransitionreport/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/reportedcheckstatetransitions/reportedcheckstatetransitions/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/checkedparameter

Exception in user code:

------------------------------------------------------------

------------------------------------------------------------

s/checkedparameters/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/applicationprocess/applicationprocess/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/parameterpool/parameterpool/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/missiondatabase/missiondatabase/*.o /home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/ground/ground/*.o " make

From this directory:

/home/assert/mbcode/Prototype/Design_Definition_File/Taste_Model/Onboard_Monitoring/binary/GlueAndBuild

Failed to compile...

To me, it smells as if there is a discrepancy between the generated Ada code and the generated C code.

Does anybody have any suggestions on how to proceed?

                Regards,

                                Gert

P.S. The complete error outputs are attached.

Gert Caspersen
Senior Engineer, Project Manager
Space Projects (DK)
Terma A/S

From: Thanassis Tsiodras [mailto:ttsiodras@xxxxxxxxxxx]
Sent: 25 April 2012 13:14
To: Gert Caspersen
Cc: taste-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [taste-users] Failing TASTE Build

On 25/4/2012 2:11 μμ, Gert Caspersen wrote:

                Hi Thanassis,

OK, this solved the problem. Thanks for your quick response time.

No pb.

Does this imply that I may delete the files "TASTE-Directives.aadl" and "TASTE-Directives.asn" or are they used somewhere else?

No - the TASTE Directives are still used for various reasons ; they are simply not referenced in the IF view anymore.

Kind regards,
Thanassis.
-- 
------------------------------------------------------------
Thanassis Tsiodras, Dr.-Ing.
Semantix Information Technologies
email: ttsiodras@xxxxxxxxxxx
web  : http://www.semantix.gr
phone: (+30)2106412065
fax  : (+30)2106412068
addr.: K Tsaldari 62, 11476, Athens, GREECE
------------------------------------------------------------
--

ESA - European Space Agency

Maxime Perrotin

TASTE Project manager

PROBA V - PROBA 3 Software engineer

System, Software and Technology Department

ESTEC

Keplerlaan 1, PO Box 299

NL-2200 AG Noordiwjk, The Netherlands

maxime.perrotin@xxxxxxx | www.esa.int

+31 (0)71 565 4923 | Fax +31 (0)71 565 5420
This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender.
 
Please consider the environment before printing this email.

ESA - European Space Agency

Maxime Perrotin

TASTE Project manager

PROBA V - PROBA 3 Software engineer

System, Software and Technology Department

ESTEC

Keplerlaan 1, PO Box 299

NL-2200 AG Noordiwjk, The Netherlands

maxime.perrotin@xxxxxxx | www.esa.int

+31 (0)71 565 4923 | Fax +31 (0)71 565 5420

This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.