[chbot] Issue with avr-gcc and ATtiny3227

[Mark Atherton]

Thank you everyone for your comments.

FYI the path used by the linker (ld.exe) is hard wired into the toolchain.

I ended up finding a build of the avr-gcc toolchain where someone else 
had already integrated the required modules to support the newer 
avr0/1/2 parts and everything is fine now.

Still can't find out what I was doing wrong, but ho-hum, forwards and 
upwards.

HNY, Mark




On 03-Jan-25 1:10 PM, Trevor Wignall wrote:
> The "../" could still cause a problem for ld.exe if it uses that path to 
> find crtattiny3227.o. ld.exe may use different code to parse the path 
> than the operating system that runs ld.exe. If you can't think of 
> something else to try, it may be worth trying to remove the "../".
> 
> Good luck Jim.
> 
> Trevor
> 
> On Fri, Jan 3, 2025 at 12:21 PM Helmut Walle <helmut.walle at gmail.com 
> <mailto:helmut.walle at gmail.com>> wrote:
> 
>     __
> 
>     But... the "../" are all in the path to ld.exe, and from the error
>     message this appears to be found and run just fine - the error
>     message says that ld cannot find crtattiny3227.o but we do not see
>     from the error message where it is looking for the object file. That
>     information would presumably be part of the library path
>     configuration, or it may be passed to ld as a command-line argument.
>     Are there differences in how the compiler and / or link editor are
>     called depending on the chip?
> 
>     On 03/01/2025 10:13, Synco Reynders wrote:
>>     Happy New Year Mark,
>>       did you solve it?
>>     My bet is on the number of ../ or possibly the handling of ./ in
>>     the middle of the path. It could be related to the c: at the
>>     start? Have you tried it on a /home system? :-) I've just pulled
>>     out a Tiny85 project again, and have been enjoying using:
>>     https://github.com/micronucleus/micronucleus
>>     <https://github.com/micronucleus/micronucleus>
>>     /s
>>
>>     On Wed, 1 Jan 2025 at 14:42, Mark Atherton <markaren1 at xtra.co.nz
>>     <mailto:markaren1 at xtra.co.nz>> wrote:
>>
>>         Hi All,
>>
>>         I have been using avr-gcc 7.30 by way of a makefile for use
>>         with the
>>         ATmega328P target without any problems for ages,
>>
>>         A couple of months ago the ATtiny404 was added, by downloading
>>         and
>>         installing the 4 required files from the Microchip site
>>         device-packs
>>         (packs.download.microchip.com
>>         <http://packs.download.microchip.com>). Again, without any issues.
>>
>>         A couple of days ago the  ATtiny3227 was added using the same
>>         process as
>>         above. All required C files compile OK, but the linker claims
>>         that it
>>         can’t find crtattiny3227.o, which is odd since it is in the same
>>         directory as crtattiny404.o (which works).
>>
>>         Full error message is
>>         c:/programfiles/avr8/bin/../lib/gcc/avr/7.3.0/../../../../avr/bin/ld.exe:
>>         cannot find crtattiny3227.o: No such file or directory
>>
>>         <yes, there is a directory called programfiles>
>>
>>         Finally I repeated the above for the ATtiny827 and avr-gcc has
>>         no idea
>>         what an attiny827 is !
>>
>>         This is the most bewildering collection of faults I have seen
>>         for ages.
>>         I guess that the attiny device-pack which was downloaded could be
>>         corrupt (I have tried twice).
>>
>>         Just found that the free XC8 compiler supports the 3227, just
>>         hope it
>>         can be run from the command line.
>>
>>         Thoughts please.
>>
>>         HNY, Mark
>>
>>         _______________________________________________
>>         Chchrobotics mailing list Chchrobotics at lists.ourshack.com
>>         <mailto:Chchrobotics at lists.ourshack.com>
>>         https://lists.ourshack.com/mailman/listinfo/chchrobotics
>>         <https://lists.ourshack.com/mailman/listinfo/chchrobotics>
>>         Mail Archives:
>>         http://lists.ourshack.com/pipermail/chchrobotics/
>>         <http://lists.ourshack.com/pipermail/chchrobotics/>
>>         Meetings usually 3rd Monday each month. See
>>         http://kiwibots.org <http://kiwibots.org> for venue,
>>         directions and dates.
>>         When replying, please edit your Subject line to reflect new
>>         subjects.
>>
>>
>>     _______________________________________________
>>     Chchrobotics mailing listChchrobotics at lists.ourshack.com  <mailto:Chchrobotics at lists.ourshack.com>
>>     https://lists.ourshack.com/mailman/listinfo/chchrobotics  <https://lists.ourshack.com/mailman/listinfo/chchrobotics>
>>     Mail Archives:http://lists.ourshack.com/pipermail/chchrobotics/  <http://lists.ourshack.com/pipermail/chchrobotics/>
>>     Meetings usually 3rd Monday each month. Seehttp://kiwibots.org  <http://kiwibots.org>  for venue, directions and dates.
>>     When replying, please edit your Subject line to reflect new subjects.
>     _______________________________________________
>     Chchrobotics mailing list Chchrobotics at lists.ourshack.com
>     <mailto:Chchrobotics at lists.ourshack.com>
>     https://lists.ourshack.com/mailman/listinfo/chchrobotics
>     <https://lists.ourshack.com/mailman/listinfo/chchrobotics>
>     Mail Archives: http://lists.ourshack.com/pipermail/chchrobotics/
>     <http://lists.ourshack.com/pipermail/chchrobotics/>
>     Meetings usually 3rd Monday each month. See http://kiwibots.org
>     <http://kiwibots.org> for venue, directions and dates.
>     When replying, please edit your Subject line to reflect new subjects.
> 
> 
> _______________________________________________
> Chchrobotics mailing list Chchrobotics at lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/chchrobotics
> Mail Archives: http://lists.ourshack.com/pipermail/chchrobotics/
> Meetings usually 3rd Monday each month. See http://kiwibots.org for venue, directions and dates.
> When replying, please edit your Subject line to reflect new subjects.