Compile Problems

19 views
Skip to first unread message

Mark Cohen

unread,
Jun 17, 2010, 5:06:13 PM6/17/10
to Gen3 Firmware Development
Hi,

This is the first time I tried to compile the firmware and I am
getting the following errors. Any help would be appreciated.

Thanks.

C:\msysgit\msysgit\G3Firmware\v2>scons
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
C:\arduino\hardware\tools\avr\bin/avr-g++ /Fobuild\boards
\rrmbv12\Motherboard.ob
j /c build\boards\rrmbv12\Motherboard.cc /TP -DF_CPU=16000000L -
mmcu=atmega644p
-g -Os -w -fno-exceptions -ffunction-sections -fdata-sections /Isrc
\shared /Ibui
ld\boards\rrmbv12 /Ibuild
avr-g++: /Fobuild\boards\rrmbv12\Motherboard.obj: No such file or
directory
avr-g++: /c: No such file or directory
avr-g++: /TP: No such file or directory
avr-g++: /Isrc\shared: No such file or directory
avr-g++: /Ibuild\boards\rrmbv12: No such file or directory
avr-g++: /Ibuild: No such file or directory
In file included from build\boards\rrmbv12\/Motherboard.hh:30,
from build\boards\rrmbv12\Motherboard.cc:22:
build\boards\rrmbv12\/UART.hh:21:21: error: Packet.hh: No such file or
directory

In file included from build\boards\rrmbv12\/Motherboard.hh:31,
from build\boards\rrmbv12\Motherboard.cc:22:
build\boards\rrmbv12\/StepperInterface.hh:21:22: error: AvrPort.hh: No
such file
or directory
In file included from build\boards\rrmbv12\Motherboard.cc:22:
build\boards\rrmbv12\/Motherboard.hh:32:20: error: Types.hh: No such
file or dir
ectory
build\boards\rrmbv12\Motherboard.cc:24:23: error: Steppers.hh: No such
file or d
irectory
build\boards\rrmbv12\Motherboard.cc:25:22: error: Command.hh: No such
file or di
rectory
In file included from build\boards\rrmbv12\/Motherboard.hh:30,
from build\boards\rrmbv12\Motherboard.cc:22:
build\boards\rrmbv12\/UART.hh:38: error: 'InPacket' does not name a
type
build\boards\rrmbv12\/UART.hh:39: error: 'OutPacket' does not name a
type
In file included from build\boards\rrmbv12\/Motherboard.hh:31,
from build\boards\rrmbv12\Motherboard.cc:22:
build\boards\rrmbv12\/StepperInterface.hh:43: error: 'Pin' does not
name a type
build\boards\rrmbv12\/StepperInterface.hh:44: error: 'Pin' does not
name a type
build\boards\rrmbv12\/StepperInterface.hh:45: error: 'Pin' does not
name a type
build\boards\rrmbv12\/StepperInterface.hh:46: error: 'Pin' does not
name a type
build\boards\rrmbv12\/StepperInterface.hh:47: error: 'Pin' does not
name a type
build\boards\rrmbv12\/StepperInterface.hh:52: error: expected ',' or
'...' befor
e '&' token
build\boards\rrmbv12\/StepperInterface.hh:56: error: ISO C++ forbids
declaration
of 'Pin' with no type
build\boards\rrmbv12\/StepperInterface.hh: In constructor
'StepperInterface::Ste
pperInterface(int)':
build\boards\rrmbv12\/StepperInterface.hh:57: error: class
'StepperInterface' do
es not have any field named 'dir_pin'
build\boards\rrmbv12\/StepperInterface.hh:57: error: 'dir' was not
declared in t
his scope
build\boards\rrmbv12\/StepperInterface.hh:58: error: class
'StepperInterface' do
es not have any field named 'step_pin'
build\boards\rrmbv12\/StepperInterface.hh:59: error: class
'StepperInterface' do
es not have any field named 'enable_pin'
build\boards\rrmbv12\/StepperInterface.hh:59: error: 'enable' was not
declared i
n this scope
build\boards\rrmbv12\/StepperInterface.hh:60: error: class
'StepperInterface' do
es not have any field named 'max_pin'
build\boards\rrmbv12\/StepperInterface.hh:60: error: 'max' was not
declared in t
his scope
build\boards\rrmbv12\/StepperInterface.hh:61: error: class
'StepperInterface' do
es not have any field named 'min_pin'
build\boards\rrmbv12\/StepperInterface.hh:61: error: 'min' was not
declared in t
his scope
In file included from build\boards\rrmbv12\Motherboard.cc:22:
build\boards\rrmbv12\/Motherboard.hh: At global scope:
build\boards\rrmbv12\/Motherboard.hh:43: error: 'micros_t' does not
name a type
build\boards\rrmbv12\/Motherboard.hh:70: error: 'micros_t' does not
name a type
build\boards\rrmbv12\Motherboard.cc: In constructor
'Motherboard::Motherboard()'
:
build\boards\rrmbv12\Motherboard.cc:34: error: 'PortC' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:34: error: 'Pin' was not declared
in this sc
ope
build\boards\rrmbv12\Motherboard.cc:34: error: 'PortD' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:37: error: 'PortA' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc: In member function 'void
Motherboard::reset
()':
build\boards\rrmbv12\Motherboard.cc:64: error: 'class UART' has no
member named
'in'
build\boards\rrmbv12\Motherboard.cc:66: error: 'class UART' has no
member named
'in'
build\boards\rrmbv12\Motherboard.cc:79: error: 'PortB' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:79: error: 'Pin' was not declared
in this sc
ope
build\boards\rrmbv12\Motherboard.cc: At global scope:
build\boards\rrmbv12\Motherboard.cc:84: error: 'micros_t' does not
name a type
build\boards\rrmbv12\Motherboard.cc: In member function 'void
Motherboard::doInt
errupt()':
build\boards\rrmbv12\Motherboard.cc:94: error: 'micros' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:96: error: 'command' has not been
declared
build\boards\rrmbv12\Motherboard.cc:97: error: 'steppers' has not been
declared
build\boards\rrmbv12\Motherboard.cc: In member function 'void
Motherboard::indic
ateError(int)':
build\boards\rrmbv12\Motherboard.cc:120: error: 'PortB' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:120: error: 'Pin' was not declared
in this s
cope
build\boards\rrmbv12\Motherboard.cc: In function 'void __vector_11()':
build\boards\rrmbv12\Motherboard.cc:154: error: 'PortB' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:154: error: 'Pin' was not declared
in this s
cope
build\boards\rrmbv12\Motherboard.cc:162: error: 'PortB' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:162: error: 'Pin' was not declared
in this s
cope
build\boards\rrmbv12\Motherboard.cc:168: error: 'PortB' was not
declared in this
scope
build\boards\rrmbv12\Motherboard.cc:168: error: 'Pin' was not declared
in this s
cope
scons: *** [build\boards\rrmbv12\Motherboard.obj] Error 1
scons: building terminated because of errors.

C:\msysgit\msysgit\G3Firmware\v2>

Rick Pollack

unread,
Jun 17, 2010, 5:19:42 PM6/17/10
to gen3-firmwar...@googlegroups.com
Which OS are you compiling on?

Ethan Dicks

unread,
Jun 17, 2010, 7:05:27 PM6/17/10
to gen3-firmwar...@googlegroups.com
On Thu, Jun 17, 2010 at 5:19 PM, Rick Pollack <ri...@makergear.com> wrote:
> Which OS are you compiling on?
>
> On Thu, Jun 17, 2010 at 5:06 PM, Mark Cohen <markc...@gmail.com> wrote:
>> C:\msysgit\msysgit\G3Firmware\v2>scons...

The "C:\" makes me think it's not UNIX (which means I have nothing to
suggest except changing platforms, especially since I'm seeing mixed
"/" and "\" in paths).

-ethan

Mark Cohen

unread,
Jun 17, 2010, 7:11:50 PM6/17/10
to gen3-firmwar...@googlegroups.com, gen3-firmwar...@googlegroups.com
Windows 7 using the command line


Sent from my iPad

Rick Pollack

unread,
Jun 17, 2010, 7:33:50 PM6/17/10
to gen3-firmwar...@googlegroups.com
I encountered a similar problem


C:\arduino\hardware\tools\avr\bin/avr-g++

needs to be changed to 'gcc' when compiling. I don't know SCONS and I had to play some games to get it to work...

env=Environment(CC=avr_tools_path+"/avr-gcc",
    CXX=avr_tools_path+"/avr-g++")
   
env.Tool("mingw")

env.Replace(CC=avr_tools_path+"/avr-gcc",   
    CXX=avr_tools_path+"/avr-g++",
    CPPPATH=include_paths,
    CCFLAGS=flags)
   
objs = env.Object(srcs)

Try the attached files...they replace the sconscript files in the respective build folders (rename your originals :)

Rick
SConscript mobo.zip
SConscript ec.zip

Mark Cohen

unread,
Jun 17, 2010, 7:54:11 PM6/17/10
to gen3-firmwar...@googlegroups.com

Thanks!

 

I will try this out later. I was actually expecting this to work right out of the box (LOL) when reading the Wiki. I thought it seemed too easy.

 

My goal is to see what is causing areas not to print with the v2 firmware and fix it. I suppose there is no simulator and I just have to load it and try it over and over?

 

--Mark

Mark Cohen

unread,
Jun 17, 2010, 8:01:19 PM6/17/10
to gen3-firmwar...@googlegroups.com
I can always change platforms if it doesn't work out. I work on them all. I
was just trying it on the most convenient for me as it seemed that the wiki
implied it would work with windows without modification.

-----Original Message-----
From: gen3-firmwar...@googlegroups.com
[mailto:gen3-firmwar...@googlegroups.com] On Behalf Of Ethan Dicks
Sent: Thursday, June 17, 2010 7:05 PM
To: gen3-firmwar...@googlegroups.com
Subject: Re: Compile Problems

Mark Cohen

unread,
Jun 18, 2010, 12:12:32 PM6/18/10
to gen3-firmwar...@googlegroups.com

This works fine.

 

Thanks!

 

From: gen3-firmwar...@googlegroups.com [mailto:gen3-firmwar...@googlegroups.com] On Behalf Of Rick Pollack
Sent: Thursday, June 17, 2010 7:34 PM
To: gen3-firmwar...@googlegroups.com
Subject: Re: Compile Problems

 

I encountered a similar problem

Dave M.

unread,
Aug 8, 2010, 6:40:58 PM8/8/10
to Gen3 Firmware Development
Rick, I've been putting together a tutorial for those that are having
trouble getting things together for compiling source (I haven't found
a comprehensive how-to anywhere yet). I got to the exact same point
as Mark and had the same compiler errors. But I don't understand why
you changed the scons tool to mingw, or how you knew that that was
necessary! Can you please shed some light on this? I am confused as
to why the scons files don't work right out of git... Maybe Adam can
shed some light on this as well?
Message has been deleted

Rick Pollack

unread,
Aug 8, 2010, 10:14:46 PM8/8/10
to gen3-firmwar...@googlegroups.com
I went to the scons IRC channel and asked for help :)

On Sun, Aug 8, 2010 at 7:14 PM, Dave M. <mr....@gmail.com> wrote:
(hopefully this isn't a double post -- I sent this but it didn't
appear in the group afterward so I am reposting)

Dave Matsumoto

unread,
Aug 8, 2010, 11:00:06 PM8/8/10
to gen3-firmwar...@googlegroups.com
IRC?  wow, ok.  I haven't used IRC in a while, but I'll have to keep that in mind.  Did the guys there explain to you why you needed to switch to MinGW?

Thanks!
Dave
Reply all
Reply to author
Forward
0 new messages