Re: [Paparazzi-devel] master changed, build failure.

paparazzi-devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] master changed, build failure.

From:	Urivan Flores-Saaib
Subject:	Re: [Paparazzi-devel] master changed, build failure.
Date:	Mon, 09 Jun 2014 18:48:46 -0700
User-agent:	Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

Nice!

Updating the broken link on the left menu under Development on thewebsite might be a good idea, currently it points to:


http://paparazzi.gondwana.com.au/allPlans.action

Regards,

-Urivan


On 06/09/2014 03:23 PM, Piotr Esden-Tempski wrote:

Yes we do have a CI server.

http://buildbot.paparazziuav.org/waterfall

and it indeed did expose the build error that was reported.

http://buildbot.paparazziuav.org/builders/ubuntu-14.04-64bit-master/builds/52
http://buildbot.paparazziuav.org/builders/ubuntu-14.04-64bit-master/builds/52/steps/test/logs/stdio

Cheers,
Piotr

On Jun 9, 2014, at 15:12, Urivan Flores Saaib <address@hidden> wrote:

Does Paparazi has a continuous integration server that picks the branch updates 
and builds all the targets after every commit/daily?

This issues should be easy to identify with such tool.Regards,


-Urivan Flores


------ Original message ------
From: Gautier Hattenberger
Date: 6/9/2014 10:56 AM
To: Paparazzi UAV devel list;
Subject:Re: [Paparazzi-devel] master changed, build failure.

Hi,

Thanks for reporting, it should be fixed in master now.

Gautier

Le 09/06/2014 16:58, afishindouban a écrit :

Hi

With previous master

, no

problem to build some sample.
With new master, AP target build shows error. Please check build log:

RUN 'make -C /home/ppz511/paparazzi -f Makefile.ac AIRCRAFT=Microjet_LisaM
clean_ac '
make: Entering directory `/home/ppz511/paparazzi'
Microjet_LisaM
rm -fr /home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM
make: Leaving directory `/home/ppz511/paparazzi'

DONE 'make -C /home/ppz511/paparazzi -f Makefile.ac AIRCRAFT=Microjet_LisaM
clean_ac'

RUN 'make -C /home/ppz511/paparazzi -f Makefile.ac AIRCRAFT=Microjet_LisaM
PRINT_CONFIG=1 ap.compile '
make: Entering directory `/home/ppz511/paparazzi'
-----------------------------------------------------------------------
Paparazzi version v5.1.1_testing-79-g42bb085
-----------------------------------------------------------------------
Microjet_LisaM
BUILD Microjet_LisaM, TARGET ap
make[1]: Entering directory `/home/ppz511/paparazzi'
GENERATE
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/generated/airframe.h
##################################################
   AIRFRAME MODEL: Microjet_LisaM
##################################################
GENERATE
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/generated/modules.h
Module baro_sim unloaded, target ap not supported
GENERATE
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/generated/periodic_telemetry.h
GENERATE
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/generated/settings.h
GENERATE
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/generated/autopilot_core.h
make[1]: Leaving directory `/home/ppz511/paparazzi'
make[1]: Entering directory `/home/ppz511/paparazzi'
GENERATE
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/generated/radio.h
##################################################
   RADIO MODEL: cockpitSX (easy)
##################################################
make[1]: Leaving directory `/home/ppz511/paparazzi'
make[1]: Entering directory `/home/ppz511/paparazzi'
GENERATE
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/generated/flight_plan.h
##################################################
   FLIGHT PLAN: Basic
##################################################

Warning: low altitude (185<185+25) in

  ALT="185.0"/>

GENERATE /home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/flight_plan.xml
make[1]: Leaving directory `/home/ppz511/paparazzi'
cd sw/airborne; make -j1 TARGET=ap all
Using "arch/stm32/lisa-m.ld" as ldscript for target "ap".
make[1]: Entering directory `/home/ppz511/paparazzi/sw/airborne'

GCC version: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.8.3
20140228 (release) [ARM/embedded-4_8-branch revision 208322]

CC /home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/mcu.o
CC
/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/arch/stm32/mcu_arch.o
arch/stm32/mcu_arch.c:43:1: error: unknown type name 'clock_scale_t'
   const clock_scale_t hse_25mhz_3v3_168mhz = { /* 168MHz */
   ^
arch/stm32/mcu_arch.c:44:3: error: field name not in record or union
initializer
     .pllm = 25,
     ^
arch/stm32/mcu_arch.c:44:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:45:3: error: field name not in record or union
initializer
     .plln = 336,
     ^
arch/stm32/mcu_arch.c:45:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:45:3: warning: excess elements in scalar initializer
[enabled by default]
arch/stm32/mcu_arch.c:45:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:46:3: error: field name not in record or union
initializer
     .pllp = 2,
     ^
arch/stm32/mcu_arch.c:46:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:46:3: warning: excess elements in scalar initializer
[enabled by default]
arch/stm32/mcu_arch.c:46:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:47:3: error: field name not in record or union
initializer
     .pllq = 7,
     ^
arch/stm32/mcu_arch.c:47:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:47:3: warning: excess elements in scalar initializer
[enabled by default]
arch/stm32/mcu_arch.c:47:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:48:3: error: field name not in record or union
initializer
     .hpre = RCC_CFGR_HPRE_DIV_NONE,
     ^
arch/stm32/mcu_arch.c:48:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:48:11: error: 'RCC_CFGR_HPRE_DIV_NONE' undeclared here
(not in a function)
     .hpre = RCC_CFGR_HPRE_DIV_NONE,
             ^
arch/stm32/mcu_arch.c:48:3: warning: excess elements in scalar initializer
[enabled by default]
     .hpre = RCC_CFGR_HPRE_DIV_NONE,
     ^
arch/stm32/mcu_arch.c:48:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:49:3: error: field name not in record or union
initializer
     .ppre1 = RCC_CFGR_PPRE_DIV_4,
     ^
arch/stm32/mcu_arch.c:49:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:49:12: error: 'RCC_CFGR_PPRE_DIV_4' undeclared here
(not in a function)
     .ppre1 = RCC_CFGR_PPRE_DIV_4,
              ^
arch/stm32/mcu_arch.c:49:3: warning: excess elements in scalar initializer
[enabled by default]
     .ppre1 = RCC_CFGR_PPRE_DIV_4,
     ^
arch/stm32/mcu_arch.c:49:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:50:3: error: field name not in record or union
initializer
     .ppre2 = RCC_CFGR_PPRE_DIV_2,
     ^
arch/stm32/mcu_arch.c:50:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:50:12: error: 'RCC_CFGR_PPRE_DIV_2' undeclared here
(not in a function)
     .ppre2 = RCC_CFGR_PPRE_DIV_2,
              ^
arch/stm32/mcu_arch.c:50:3: warning: excess elements in scalar initializer
[enabled by default]
     .ppre2 = RCC_CFGR_PPRE_DIV_2,
     ^
arch/stm32/mcu_arch.c:50:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:51:3: error: field name not in record or union
initializer
     .flash_config = FLASH_ACR_ICE | FLASH_ACR_DCE |
     ^
arch/stm32/mcu_arch.c:51:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:51:19: error: 'FLASH_ACR_ICE' undeclared here (not in
a function)
     .flash_config = FLASH_ACR_ICE | FLASH_ACR_DCE |
                     ^
arch/stm32/mcu_arch.c:51:35: error: 'FLASH_ACR_DCE' undeclared here (not in
a function)
     .flash_config = FLASH_ACR_ICE | FLASH_ACR_DCE |
                                     ^
arch/stm32/mcu_arch.c:52:18: error: 'FLASH_ACR_LATENCY_5WS' undeclared here
(not in a function)
                    FLASH_ACR_LATENCY_5WS,
                    ^
arch/stm32/mcu_arch.c:52:18: warning: excess elements in scalar initializer
[enabled by default]
arch/stm32/mcu_arch.c:52:18: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:53:3: error: field name not in record or union
initializer
     .apb1_frequency = 42000000,
     ^
arch/stm32/mcu_arch.c:53:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:53:3: warning: excess elements in scalar initializer
[enabled by default]
arch/stm32/mcu_arch.c:53:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c:54:3: error: field name not in record or union
initializer
     .apb2_frequency = 84000000,
     ^
arch/stm32/mcu_arch.c:54:3: error: (near initialization for
'hse_25mhz_3v3_168mhz')
arch/stm32/mcu_arch.c:54:3: warning: excess elements in scalar initializer
[enabled by default]
arch/stm32/mcu_arch.c:54:3: warning: (near initialization for
'hse_25mhz_3v3_168mhz') [enabled by default]
arch/stm32/mcu_arch.c: In function 'mcu_arch_init':
arch/stm32/mcu_arch.c:59:1: note: #pragma message: Config: We are running
luftboot, the interrupt vector is being relocated.
   PRINT_CONFIG_MSG("We are running luftboot, the interrupt vector is being
relocated.")
   ^
arch/stm32/mcu_arch.c:72:1: note: #pragma message: Config: Using 12MHz
external clock to PLL it to 72MHz.
   PRINT_CONFIG_MSG("Using 12MHz external clock to PLL it to 72MHz.")
   ^
make[1]: ***
[/home/ppz511/paparazzi/var/aircrafts/Microjet_LisaM/ap/arch/stm32/mcu_arch.o]
Error 1
make[1]: Leaving directory `/home/ppz511/paparazzi/sw/airborne'
make: *** [ap.compile] Error 2
make: Leaving directory `/home/ppz511/paparazzi'

FAILED 'make -C /home/ppz511/paparazzi -f Makefile.ac
AIRCRAFT=Microjet_LisaM PRINT_CONFIG=1 ap.compile' with code 2





--
View this message in context: 
http://lists.paparazziuav.org/master-changed-build-failure-tp15645.html
Sent from the paparazzi-devel mailing list archive at Nabble.com.

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel



--
Regards,

-Urivan Flores

[Prev in Thread]

Current Thread

[Next in Thread]

[Paparazzi-devel] master changed, build failure., afishindouban, 2014/06/09
- Re: [Paparazzi-devel] master changed, build failure., Gautier Hattenberger, 2014/06/09
- Re: [Paparazzi-devel] master changed, build failure., Urivan Flores Saaib, 2014/06/09
  - Re: [Paparazzi-devel] master changed, build failure., Piotr Esden-Tempski, 2014/06/09
    - Re: [Paparazzi-devel] master changed, build failure., Urivan Flores-Saaib <=

Prev by Date: Re: [Paparazzi-devel] master changed, build failure.
Next by Date: [Paparazzi-devel] lisa/m v2 quadrotor / current minor issues
Previous by thread: Re: [Paparazzi-devel] master changed, build failure.
Next by thread: [Paparazzi-devel] lisa/m v2 quadrotor / current minor issues
Index(es):
- Date
- Thread