Re: [avrdude-dev] Building Avrdude 6.3

2019-03-24 Thread Wayne Holder
> Did you “make clean” or otherwise clear out the directory at the same time as you deleted /opt? To completely resolve the build issue I had to completely remove the /opt tree, then remove all references to it from my $PATH setting and, finally, rebuild all the libraries I'd built with brew, as s

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-24 Thread Joerg Wunsch
As Matthew Mondor wrote: > > Maybe the OSX linker needs it, I don't know. > > It's quite possible some ranlib magic is still missing in the current > > make/automake files. > > Very likely, Darwin being a BSD variant, all the BSDs that I know need > it as well. My main development system is Free

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-24 Thread Matthew Mondor
On Sun, 24 Mar 2019 08:52:28 +0100 Joerg Wunsch wrote: > Maybe the OSX linker needs it, I don't know. > It's quite possible some ranlib magic is still missing in the current > make/automake files. Very likely, Darwin being a BSD variant, all the BSDs that I know need it as well. -- Matt __

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-24 Thread Joerg Wunsch
Am 24. März 2019 05:05:39 MEZ schrieb Joel Ray Holveck : >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. Maybe the OSX linker needs it, I don't know. It's quite possible some ranlib magi

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-23 Thread 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

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-22 Thread Joerg Wunsch
Am 23. März 2019 03:14:53 MEZ schrieb Wayne Holder : >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 c

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-22 Thread Joel Ray Holveck
On Mar 22, 2019, at 13:30, Wayne Holder wrote: > > My system is up to date with the latest version of > Xcode and is running macOS 0.14.2 (18C54) "Mojave". Just to make sure: have you launched Xcode’s GUI since you last updated it? That will set up many of the command-line tools that are neede

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-22 Thread Wayne Holder
I guess some of my problems came from having once used macPorts. So, I deleted the /opt folder, fixed my $PATH and then reran configure and make. This gets me further, but still no cigar. Tha current error is now: libtool: link: ( cd ".libs" && rm -f "libavrdude.la" && ln -s "../ libavrdude.la"

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-22 Thread Wayne Holder
It appears I had an old copy of gm4 in opt/local/bin and, when I removed it, I got much further in the process. I now have only the following errors printed: ar cru libavrdude.a libavrdude_a-config_gram.o libavrdude_a-lexer.o libavrdude_a-arduino.o libavrdude_a-avr.o libavrdude_a-avr910.o libavrd

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-22 Thread Wayne Holder
Thanks for trying to help me. When I run the command you suggested: > /bin/sh ./ylwrap lexer.l lex.yy.c lexer.c -- flex I get an immediate "gm4 had quit unexpectedly" message and no other response on the command line. And, when I then run configure and make, I get the same result as before. I

Re: [avrdude-dev] Building Avrdude 6.3

2019-03-22 Thread Joerg Wunsch
As Wayne Holder wrote: > As part of trying to diagnose the issue I'm having with serbb and the TPI > protocol (see my other thread on this topic), I decided to try and build > the 6.3 release on my Mac Pro system and then see if I could resolve the > issue by making a few tweaks to the timing bit