Re: [avrdude-dev] Building Avrdude 6.3

[Joel Ray Holveck]

Did you “make clean” or otherwise clear out the directory at the same time as 
you deleted /opt?

Did Joerg’s suggestion help?

If the answer is “no” and “yes” respectively, then I offer the following 
hypothesis.

The Unix build process doesn’t really have a good way to see that a previous 
ranlib step failed, so if it sees that the .a file exists, it assumes that 
ranlib succeeded.  (ranlib only changes the structure of an existing .a file; 
on systems that need it, it’s generally run right after the .a is created in 
the build process.)  When you reran make, it thought that ranlib succeeded 
previously, and that assumption broke the later build steps.

In Joerg’s case, it sounds like the mingw32 cross-build might not properly 
detect that it needs to run ranlib.  It’s not needed, for instance, on Linux.

joelh

> On Mar 22, 2019, at 23:49, Joerg Wunsch <address@hidden> wrote:
> 
> 
> 
> Am 23. März 2019 03:14:53 MEZ schrieb Wayne Holder <address@hidden>:
> 
>> libtool: link: gcc -Wall -g -O2 -o avrdude avrdude-main.o
>> avrdude-term.o
>> ./libavrdude.a -lusb-1.0 -lusb -framework CoreFoundation -framework
>> IOKit
>> -lftdi1 -lelf -lpthread -lm -lreadline -lncurses -ltermcap
>> 
>> ld: archive has no table of contents file './libavrdude.a' for
>> architecture
>> x86_64
> 
> I have a similar issue when cross-compiling the win32 version using mingw32. 
> I never found the actual reason, alas.
> 
> Try
> 
> ranlib libavrdude.a
> 
> and then "make" again.
> 
> 
> -- 
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> 
> _______________________________________________
> avrdude-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/avrdude-dev