You might also send the Makefile, if you have one.
On Tue, Jun 30, 2009 at 1:17 PM, Dave Camarillo <dave.camari...@gmail.com>wrote:
> Hi Jeremy, couple questions:
> -I'm assuming you have the ADC code in a separate source file, called
> -When doing a 'make', do you see something to the extent of "gcc BLA
> BLA BLA adc.c -o adc.o BLA BLA" In particular, we want to make sure
> that the corresponding ".o" file is being created.
> -When doing a 'make', toward the end, during linking (which is where
> your error is coming from), do you see it referencing the "adc.o"
> object file? If not, that would be the part of the problem.
> Can you send the full console output when running make?
> On Mon, Jun 29, 2009 at 4:59 PM, Jeremy Booth<jboo...@gmail.com> wrote:
> > When trying to compile some ADC bits and pieces, I get the following
> > main.o: In function `ADCtestTask':
> > /home/user/freertos-5.1.2-lpc23xx/BlinkyLightSample/main.c:198: undefined
> > reference to `configureADCPort'
> > collect2: ld returned 1 exit status
> > make: *** [BlinkyLightSample.elf] Error 1
> > I have a similar directory, include and makefile setup for the GPIO
> > and as far as I can tell they all match. The GPIO commands compile and
> > just fine.
> > This should show up in the latest commit to the 5.1.2Testing branch of
> > LPC2368 code.
> > Also, I could use a few pointers on getting that interworking thing set
> > If I read what Dave said earlier correctly, then I will have to recompile
> > the GCC libs, but I could have that all munged up...
> > -Jeremy
> > _______________________________________________
> > psas-avionics mailing list
> > firstname.lastname@example.org
> > http://lists.psas.pdx.edu/mailman/listinfo/psas-avionics
> psas-avionics mailing list
psas-avionics mailing list