From: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
To: R Sidhu <sidhu1f@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Using guile-ssh
Date: Sat, 16 Aug 2014 14:12:01 +0200 [thread overview]
Message-ID: <87lhqows4u.fsf@taylan.uni.cx> (raw)
In-Reply-To: <CADhE+R9cxWb34kigh0tXDZM-ErQY+FyuJ5gvFSyH9+D1z7SYXQ@mail.gmail.com> (R. Sidhu's message of "Fri, 15 Aug 2014 22:14:48 +0530")
R Sidhu <sidhu1f@gmail.com> writes:
> I am interested in using guile-ssh for file transfer. Ran into the
> following issues:
>
> 1. 'git clone
> https://github.com/artyom-poptsov/guile-ssh/releases/tag/v0.6.0' fails
> with:
> fatal:
> https://github.com/artyom-poptsov/guile-ssh/releases/tag/v0.6.0/info/refs
> not valid: is this a git repository?
Tags on GitHub can be downloaded as a .tar.gz or ZIP, but not cloned if
I'm not mistaken.
> 2. INSTALL file suggests './configure' but its missing
Short story: you need to run either ./autogen.sh, or if that doesn't
exist, run "autoreconf -fi" in the source directory.
Long story:
The ./configure script of a software package is what needs to be run on
the install-site to configure the package for the machine on which it
will be compiled and installed, but this ./configure script is rarely
written by hand, because it must be in the Bourne shell language to be
highly portable across Unix machines, which is a horrible language.
Most commonly, there is a configure.ac file which is written in the more
special-purpose and high-level autoconf language, and the software's
author runs the autoconf command to turn this into a ./configure script
before packaging and shipping the software. Therefore, when you fetch
the bare source code of a project, you usually have a configure.ac file
but not the ./configure script which it would generate. Often for
convenience there is a tiny ./autogen.sh script which runs autoconf and
maybe some other things for you (specifically automake), but nowadays
usually running "autoreconf -fi" is the only thing that needs to be
done.
> 3. Installation instructions in doc/ directory (texinfo files) suggest
> 'autoreconf -if' which fails with:
> configure.ac:55: error: possibly undefined macro: AC_DEFINE
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
I had this problem more than once already but keep forgetting what the
solution was.
Do you have pkg-config installed? Do you have pkg-config files in
non-standard places, like $HOME/usr/lib/pkgconfig, or
$HOME/.guix-profile/lib/pkgconfig? If so you'll need to set
PKG_CONFIG_PATH to a colon-separated list of such directories. (Best to
'export' that in ~/.profile or ~/.bash_login or so.)
Do you have a recent version of GNU m4 installed?
> 4. While initial steps seem clear (establishing session,
> authenticating and creating channel), not clear how to perform file
> transfer.
I've never used guile-ssh so this is a shot in the dark: maybe a simple
read-char / write-char loop to read and write the bytes in a file one by
one?
> Appreciate work done on guile-ssh so far. Look forward to help re
> above.
>
> Regards
> sidhu1f
Hope someone can clear questions 3 and 4.
Taylan
next prev parent reply other threads:[~2014-08-16 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 16:44 Using guile-ssh R Sidhu
2014-08-16 12:12 ` Taylan Ulrich Bayirli/Kammer [this message]
2014-08-17 10:49 ` R Sidhu
[not found] <mailman.81.1408291224.11683.guile-user@gnu.org>
2014-08-17 20:25 ` Artyom Poptsov
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhqows4u.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=guile-user@gnu.org \
--cc=sidhu1f@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).