public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: "David A. Desrosiers" <hacker@gnu-designs.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Evolution Pilot Conduit
Date: 07 Jan 2002 01:21:18 +0100	[thread overview]
Message-ID: <1010362878.951.8.camel@fluffy> (raw)
In-Reply-To: <Pine.LNX.4.43.0201061551040.6853-100000@broccoli.geek.box>

[-- Attachment #1: Type: text/plain, Size: 2592 bytes --]

mån 2002-01-07 klockan 00.53 skrev David A. Desrosiers:
> 
> > As I said, it _do_ find iconv (or so says the configure-script) but it
> > doesn't set it in the pi-config.h
> 
> 	Ok, this is a slightly different issue then. Noted.
> 
> > Yes, it might be a problem either in 0.9.6 (since it's not a supported
> > release) or in Gentoo Linux.
> 
> 	0.9.6 is not a release at all, unsupported or not. The versions in
> the official cvs jumped from 0.9.5 to 0.10.1, there was never a 0.9.6,
> unless someone made a tarball from the 0.9.5 cvs sources, changed the
> version to make it appear that there was a "newer" release, and let it out
> into the wild.

Which I suppose is what happend:
http://www.eskil.org/gnome-pilot/download/tarballs/pilot-link-0.9.6.tar.gz

> > So if you try to cool down a bit I'll try to figure out what was going
> > wrong (might very well be 0.9.6 since I haven't seen these problems
> > before).
> 
> 	I would suggest sticking with official releases, because in
> unofficial rogue versions, you never know what you'll find, or what has been
> changed.

Ok, I've (re)-tracked down the problem. And the error is in 0.9.6
(worked fine with 0.9.5), sorry to made it look like it was your fault
with it was the one that released 0.9.6 (which very much sounds like an
official newer release than 0.9.6).

configure:7065: checking for gnu_get_libc_version
configure:7102: gcc -o conftest -g -O2     conftest.c  -lm >&5
configure:7105: $? = 0
configure:7108: test -s conftest
configure:7111: $? = 0
configure:7121: result: yes
configure:7131: checking if system iconv handles CP1252
configure:7173: gcc -c -g -O2   conftest.c >&5
configure: In function `main':
configure:7155: warning: passing arg 2 of `iconv' from incompatible
pointer typeconfigure: At top level:
configure:7164: redefinition of `main'
configure:7144: `main' previously defined here
configure: In function `main':
configure:7164: number of arguments doesn't match prototype
configure:7144: prototype declaration
configure:7165: `echo' undeclared (first use in this function)
configure:7165: (Each undeclared identifier is reported only once
configure:7165: for each function it appears in.)
configure:7165: parse error before string constant
configure:7166: `have_iconv' undeclared (first use in this function)
configure:7167: `yes' undeclared (first use in this function)

When will you guys release 0.10.1?

Regards,
  Mikael Hallendal

-- 
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

       reply	other threads:[~2002-01-07  0:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.43.0201061551040.6853-100000@broccoli.geek.box>
2002-01-07  0:21 ` Mikael Hallendal [this message]
2002-01-06 21:19 [gentoo-dev] Re: Evolution Pilot Conduit David A. Desrosiers
2002-01-06 21:55 ` Mikael Hallendal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1010362878.951.8.camel@fluffy \
    --to=hallski@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=hacker@gnu-designs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox