On Sun, Jul 25, 2010 at 11:03 PM, Gregg Levine <[email protected]> wrote: > On Sun, Jul 25, 2010 at 4:46 PM, Paul Alfille <[email protected]> wrote: >> Will you contact him? >> >> On Sun, Jul 25, 2010 at 4:44 PM, Gregg Levine <[email protected]> >> wrote: >>> >>> On Sun, Jul 25, 2010 at 4:39 PM, Paul Alfille <[email protected]> >>> wrote: >>> > Hi Greg, >>> > >>> > Slackware issue. Can you help? >>> > >>> > Thanks, >>> > Paul >>> > >>> > ---------- Forwarded message ---------- >>> > From: SourceForge.net <[email protected]> >>> > Date: Sun, Jul 25, 2010 at 3:37 PM >>> > Subject: [Owfs-forums] [Help] compil error with owfs-2.7p29 and next >>> > To: [email protected] >>> > >>> > >>> > >>> > The following forum message was posted by lebardix at >>> > http://sourceforge.net/projects/owfs/forums/forum/292718/topic/3783865: >>> > >>> > Hi, >>> > I am using 1-wire sensors and solenoid to control irrigation by fuzzy >>> > logic >>> > in my garden :) >>> > >>> > I\'m using pc soekris 4801 with Damn Small Linux (4.4.3) to control >>> > 1-wire >>> > bus. the owfs release is 2.7p4 but i have some >>> > problems with Moisture Sensor (Hobby board see >>> > >>> > [b]http://happyfarming.com/2009/05/03/soil-moisture-sensor-circuit-explained/[/b] >>> > ). and other problems ... (deconnect, stopped ... when i access to >>> > moissture >>> > sensor) >>> > >>> > Also I think to update to the last release 2.7p38. >>> > >>> > Because it\'s very difficult to compil with DSL tools, i am using >>> > slackware >>> > 10.2 ( kernel 2.4.31 as DSL ). >>> > >>> > But errors appears (with libtool) when i\'am build >>> > owfs-2.7p[29|..|37|38|....]. >>> > >>> > No build error with owfs2.7p28 and previous. >>> > I can post build logs ... >>> > >>> > When my project will be functional, I sent you documentation. >>> > >>> > To date, the irrigation programs work. the acquisition parameters >>> > (temperature, humidity, wind, sunshine, day length ...) is partial does >>> > not >>> > allow me to use my modules in fuzzy logic control >>> > >>> > What version should I use? 2.7p28 or over ? >>> > >>> > thank you for your beautiful project >>> > >>> > Best Regards >>> > I am a bad user of English /o\\ >>> > >>> > Marc >>> > >>> > nota: >>> > I have see what the new release after 2.7p28 use autoconf 1.11.1 (in >>> > slack >>> > 10.2 is 1.9.5), also i have regenerate Makeconfig.in with automake et >>> > autoconf, and i have also cp my /usr/bin/libtool in >>> > src/scripts/install/install.sh >>> > >>> > But always end with this error >>> > configure: creatong libtool >>> > configure: error: tag name \"CXX\"already exist >>> >>> Hello! >>> Excellent question. I do remember seeing that happen trying to get >>> those versions to work with 10.2. Unless the question can post >>> complete logs here, or for that matter someplace online, we can't help >>> him. Ideally that should not happen. >>> >>> He may need to reinstall his entire developers tool set. >>> >>> >>> ----- >>> Gregg C Levine [email protected] >>> "This signature fought the Time Wars, time and again." >> >> > Hello! > Paul, I've been thinking. What about downing the entire forum thing on > the site? The best way for a potential user of the kit is to ask > questions on the list? And to try out the kit on their distribution. > It happens the last time I used Slackware 10.2 on a system was about > November of last year. That system was running 10.2 without problems. > > He would need to join the list, and make his logs publically readable. > I'm not say we'd need access to his system.... That's not it, simply > put his logs onto that paste bin thing and provide for us the > location. > > The big problem is that I don't use Hobby Board devices, I am familiar > with, however, the way Slackware's tool chain as provided by the GNU > group, ideally the problem looks to be an issue with how they were > installed. It rarely happens, but I suspect that the libtool device > (or scripting entity) was corrupted. > > Right now I am making plans to install 10.2 on an appropriate drive > sizes and hardware, and do an installation of that release of OWFS. > > If I can work out the illogical ideas they use for packaging, then > I'll be prepared to make up a typical package for OWFS and offer to > send that to him. > > But remember I know enough to make the whole idea to work, I'm not an > expert, the kind who believes he can offer his services for some > idiotic fee. > ----- > Gregg C Levine [email protected] > "This signature fought the Time Wars, time and again." >
Hello! Paul, I just completed building my "test Slackware-10.2 system". And naturally I then grabbed the things to make OWFS work. It turns out that the problem our French correspondent reported was first reported by me. I don't know why I didn't recall that, but yes I did see exactly that problem, back about the turn of the century or so, perhaps as much as seven years earlier. Your response then was to update things and produce a p30 release. He has since found a work around, the forum response indicates that he selected the p28 release and got that to build properly. I suspect that the run-time library build methods that are supposed to be consistent across Linux distributions actually were not as such earlier on. Now they are. Also of course the way we write C code does drift with time. Yours is getting better at it. However it did repeat itself for the p30, (here) I believe then I simply upgraded to 11.0 since by that time Pat released that version. Now that he's found a solution, we can basically consider this problem closed. ----- Gregg C Levine [email protected] "This signature fought the Time Wars, time and again." ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
