<div dir="ltr"><div>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 "../".</div><div><br></div><div>Good luck Jim.</div><div><br></div><div>Trevor<br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Jan 3, 2025 at 12:21 PM Helmut Walle <<a href="mailto:helmut.walle@gmail.com">helmut.walle@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p>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?<br>
</p>
<div>On 03/01/2025 10:13, Synco Reynders
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Happy New Year Mark, </div>
<div> did you solve it?</div>
<div>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: <a href="https://github.com/micronucleus/micronucleus" target="_blank">https://github.com/micronucleus/micronucleus</a></div>
<div>/s</div>
<div><br>
</div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 1 Jan 2025 at
14:42, Mark Atherton <<a href="mailto:markaren1@xtra.co.nz" target="_blank">markaren1@xtra.co.nz</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
All,<br>
<br>
I have been using avr-gcc 7.30 by way of a makefile for
use with the <br>
ATmega328P target without any problems for ages,<br>
<br>
A couple of months ago the ATtiny404 was added, by
downloading and <br>
installing the 4 required files from the Microchip site
device-packs <br>
(<a href="http://packs.download.microchip.com" rel="noreferrer" target="_blank">packs.download.microchip.com</a>).
Again, without any issues.<br>
<br>
A couple of days ago the ATtiny3227 was added using the
same process as <br>
above. All required C files compile OK, but the linker
claims that it <br>
can’t find crtattiny3227.o, which is odd since it is in
the same <br>
directory as crtattiny404.o (which works).<br>
<br>
Full error message is <br>
c:/programfiles/avr8/bin/../lib/gcc/avr/7.3.0/../../../../avr/bin/ld.exe:
<br>
cannot find crtattiny3227.o: No such file or directory<br>
<br>
<yes, there is a directory called programfiles><br>
<br>
Finally I repeated the above for the ATtiny827 and avr-gcc
has no idea <br>
what an attiny827 is !<br>
<br>
This is the most bewildering collection of faults I have
seen for ages. <br>
I guess that the attiny device-pack which was downloaded
could be <br>
corrupt (I have tried twice).<br>
<br>
Just found that the free XC8 compiler supports the 3227,
just hope it <br>
can be run from the command line.<br>
<br>
Thoughts please.<br>
<br>
HNY, Mark<br>
<br>
_______________________________________________<br>
Chchrobotics mailing list <a href="mailto:Chchrobotics@lists.ourshack.com" target="_blank">Chchrobotics@lists.ourshack.com</a><br>
<a href="https://lists.ourshack.com/mailman/listinfo/chchrobotics" rel="noreferrer" target="_blank">https://lists.ourshack.com/mailman/listinfo/chchrobotics</a><br>
Mail Archives: <a href="http://lists.ourshack.com/pipermail/chchrobotics/" rel="noreferrer" target="_blank">http://lists.ourshack.com/pipermail/chchrobotics/</a><br>
Meetings usually 3rd Monday each month. See <a href="http://kiwibots.org" rel="noreferrer" target="_blank">http://kiwibots.org</a>
for venue, directions and dates.<br>
When replying, please edit your Subject line to reflect
new subjects.</blockquote>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Chchrobotics mailing list <a href="mailto:Chchrobotics@lists.ourshack.com" target="_blank">Chchrobotics@lists.ourshack.com</a>
<a href="https://lists.ourshack.com/mailman/listinfo/chchrobotics" target="_blank">https://lists.ourshack.com/mailman/listinfo/chchrobotics</a>
Mail Archives: <a href="http://lists.ourshack.com/pipermail/chchrobotics/" target="_blank">http://lists.ourshack.com/pipermail/chchrobotics/</a>
Meetings usually 3rd Monday each month. See <a href="http://kiwibots.org" target="_blank">http://kiwibots.org</a> for venue, directions and dates.
When replying, please edit your Subject line to reflect new subjects.</pre>
</blockquote>
</div>
_______________________________________________<br>
Chchrobotics mailing list <a href="mailto:Chchrobotics@lists.ourshack.com" target="_blank">Chchrobotics@lists.ourshack.com</a><br>
<a href="https://lists.ourshack.com/mailman/listinfo/chchrobotics" rel="noreferrer" target="_blank">https://lists.ourshack.com/mailman/listinfo/chchrobotics</a><br>
Mail Archives: <a href="http://lists.ourshack.com/pipermail/chchrobotics/" rel="noreferrer" target="_blank">http://lists.ourshack.com/pipermail/chchrobotics/</a><br>
Meetings usually 3rd Monday each month. See <a href="http://kiwibots.org" rel="noreferrer" target="_blank">http://kiwibots.org</a> for venue, directions and dates.<br>
When replying, please edit your Subject line to reflect new subjects.</blockquote></div>