headers
Harry Putnam | 2 Apr 2002 08:33
Favicon

Whats up with the make process?

Sorry to be a pest, but I haven't been using tramp for quite
so downloaded latest latest cvs, and immediately ran into trouble. 

This problem is occuring on a newly installed Freebsd 4.5-SNAP
Running Emacs-21.2

The info file says:
   * Optionally byte-compile all files in the Lisp directory,
     `~/emacs/tramp/lisp/', by issuing a command like the following
     from that directory:
          make EMACS=emacs all            # for Emacs users
          make EMACS=xemacs all           # for XEmacs users

So, all I'm supposed to do is cd to lisp and run:
 make EMACS=emacs all

What's this cheese all about?

$  make EMACS=emacs all

"Makefile", line 8: Need an operator
"Makefile", line 10: Need an operator
make: fatal errors encountered -- cannot continue

Sorry, I don't know much about Makefiles so couldn't really tell what
to edit to make it work.
Permalink | Reply | 12 comments |
headers
Kai Großjohann | 2 Apr 2002 10:12
Picon
Picon

Re: Whats up with the make process?

Harry Putnam <reader <at> newsguy.com> writes:

> The info file says:
>    * Optionally byte-compile all files in the Lisp directory,
>      `~/emacs/tramp/lisp/', by issuing a command like the following
>      from that directory:
>           make EMACS=emacs all            # for Emacs users
>           make EMACS=xemacs all           # for XEmacs users
>
> So, all I'm supposed to do is cd to lisp and run:
>  make EMACS=emacs all

Actually, I think the idea is to cd to ~/emacs/tramp, not
~/emacs/tramp/lisp.  Hm.  Got to revisit the instructions, there.

But I think that your problem is that the Makefile wants a GNU make.
So try "gmake" instead of "make".

I wanted to do a real Autoconf setup, but I was too lazy.  And I
figure that Tramp is already part of XEmacs and will be part of Emacs
soon, so why bother...  But I think that the Autoconf setup should be
done anyway.  Is anyone willing to do that?

kai
--

-- 
Silence is foo!
Permalink | Reply | 11 comments |
headers
Harry Putnam | 2 Apr 2002 11:42
Favicon

Re: Whats up with the make process?

Kai.Grossjohann <at> CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Harry Putnam <reader <at> newsguy.com> writes:
>
>> The info file says:
>>    * Optionally byte-compile all files in the Lisp directory,
>>      `~/emacs/tramp/lisp/', by issuing a command like the following
>>      from that directory:
>>           make EMACS=emacs all            # for Emacs users
>>           make EMACS=xemacs all           # for XEmacs users
>>
>> So, all I'm supposed to do is cd to lisp and run:
>>  make EMACS=emacs all
>
> Actually, I think the idea is to cd to ~/emacs/tramp, not
> ~/emacs/tramp/lisp.  Hm.  Got to revisit the instructions, there.

I tried that first, it gives even more errors, but then noticed
that the info file says explicitly to do it from `tramp/lisp'
But it was as you guessed.. It needed `gmake'.  I forgot that the
various bsds don't always use gnu stuff by default like linux distros
do.

And of course, I went ahead and byte compiled by hand, so not a
serious problem in any event.

> But I think that your problem is that the Makefile wants a GNU make.
> So try "gmake" instead of "make".

Yup..
(Continue reading)

Permalink | Reply | 10 comments |
headers
Kai Großjohann | 2 Apr 2002 13:29
Picon
Picon

Re: Whats up with the make process?

Harry Putnam <reader <at> newsguy.com> writes:

> If you gave me a brief outline of what is supposed to happen (I mean
> generally, just from off the top of your head) I may be able to figure
> out the rest and get it done.

That's great!  Thanks so much for helping.  If you look at the Gnus
or W3 source directory, you'll see a configure script.  (I'm sure you
have used it.)  There are various *.in files and an aclocal.m4 which
are used to create the non-*.in files.  To do this, run "autoconf",
maybe "aclocal" first.

So: create Makefile.in, configure.in and aclocal.m4, then run
"aclocal", then "autoconf", and you should get Makefile and configure.

I'm sure the GNU Autoconf manual has the full story, but I've not
looked at it much.

> That little section of the info manual does seem to indicate the `lisp'
> directory, but probably only fooled a few people.  If I patch the
> small info error against the current cvs, should I just post the patch
> here or send it somewhere else?

Send patch here.  Thanks!

kai
--

-- 
Silence is foo!
Permalink | Reply | 6 comments |
headers
Harry Putnam | 3 Apr 2002 18:06
Favicon

Re: Whats up with the make process?

Harry Putnam <reader <at> newsguy.com> writes:

[Note: This about a revisoin to info manual -HP]
> That little section of the info manual does seem to indicate the `lisp'
> directory, but probably only fooled a few people.  If I patch the
> small info error against the current cvs, should I just post the patch
> here or send it somewhere else?

I've written a small revision for the info manual, and also decided to
try my hand at one of the todo items in it.  The one about
install-info and Debian gnu/linux.

Debians own install-info differs from gnu install-info in that it will
not create a dir file for you.  But needs at least a skeleton dir file
and then it will insert an entry for you.  But needs to have a section
name fed to it.   Like this:

install-info --section REGEX NEW --infodir=~/emacs/tramp/texi tramp.info

Note `infodir' gives only the directory, not the file name, the file must
already be there and be named `dir'.

If it doesn't find REGEX alread in the dir file it will create a
section called NEW.

I wondered if there is a stock section Tramp is usually included in,
that I can include in that info section

I've also written a small perl script that will generate the needed
skeleton for you (on Debian systems) by extracting the head of the the
(Continue reading)

Permalink | Reply | 2 comments |
headers
Harry Putnam | 3 Apr 2002 18:31
Favicon

Re: Whats up with the make process?

Harry Putnam <reader <at> newsguy.com> writes:

> [From install section of manual]
> Unchanged
> ==================================================
>
>    * Choose a directory, say `~/emacs/'.  Change into that directory
>      and unpack the tarball.  This will give you a directory
>      `~/emacs/tramp/' which contains subdirectories `lisp' for the
>      Lisp code and `texi' for the documentation.

I lied, above is changed, so that it no longer says to run make in
emacs/tramp/lisp
Permalink | Reply | 0 comments |
headers
Harry Putnam | 3 Apr 2002 21:45
Favicon

Re: Whats up with the make process?

Harry Putnam <reader <at> newsguy.com> writes:

> }
> ## Print the captured last line and an extra newline.
> print "$last_line\n\n";
> close(SOURCE_FILE);
> close(TARGET_DIR_FILE);

A minor fix for the script.  Above neglected to print $last_line to
target file and only prints to stdout

## Print the captured last line and an extra newline.
print "$last_line\n\n";
print  TARGET_DIR_FILE "$last_line\n\n";
close(SOURCE_FILE);
close(TARGET_DIR_FILE);
Permalink | Reply | 0 comments |
headers
Harry Putnam | 3 Apr 2002 23:24
Favicon

Re: Whats up with the make process?

Kai.Grossjohann <at> CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> That's great!  Thanks so much for helping.  If you look at the Gnus
> or W3 source directory, you'll see a configure script.  (I'm sure you
> have used it.)  There are various *.in files and an aclocal.m4 which
> are used to create the non-*.in files.  To do this, run "autoconf",
> maybe "aclocal" first.
>
> So: create Makefile.in, configure.in and aclocal.m4, then run
> "aclocal", then "autoconf", and you should get Makefile and configure.
>
> I'm sure the GNU Autoconf manual has the full story, but I've not
> looked at it much.

I read man autoconf through.  It seems to be saying I should run
`autoscan' in tramp, which generates configure.scan.  I'm then told to
look at configure.scan and `make sure its ok'.  man autoconf expects
me to know what is `ok'

Then rename configure.scan to configure.in and run autoconf.  Doesn't
really say I need to create aclocal or aclocal.mf, only that autoconf
will use them.  Seems to indicate they are part of autoconf setup and
definitely has nothing I understand to say about what is in them.

Looking at examples in gnus does nothing to clear it up and in fact
only further confuses me.  There are enough if elses in there to choke
two mules.

So renamed configure.scan to configure.in  and run autoconf
(Continue reading)

Permalink | Reply | 5 comments |
headers
Spencer L. Swift | 3 Apr 2002 23:45
Picon

Re: tramp ($Id: tramp.el,v 2.94 2002/03/25 16:32:25 kaig Exp $); Saving a TRAMP'ed file hangs FSF emacs 21.1.

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann <at> CS.Uni-Dortmund.DE> writes:

Hello Kai,

Thought I would give you a little update.

    > You could use an inline method (such as sm) for this particular
    > host.  Do you think that could work?

It could, but sadly it didn't.  The remote machine doesn't have
mimeencode/decode.  I tired uudecode/encode, but the remote decode
program refused to print to stdout, so your simple test failed.  I
tried several tweaks on the piped command, but got nothing to work.

However...

    > I see.  Hm.  I wonder what is happening here.  Can you make a shell
    > script which does useful things, like perhaps:

I made a shell script just like you suggested.

lonestar(132)$ cat ~/bin/scp.sh 
#!/bin/sh
echo starting scp >> /tmp/foo
strace -f scp "$ <at> " 2>/tmp/foo
echo scp done >> /tmp/foo
exit 0

This works fine from within ielm and tramp!  I made a special method
for my one trouble machine where the rcp-command is set to "scp.sh"
(Continue reading)

Permalink | Reply | 1 comment |
headers
Colin Marquardt | 4 Apr 2002 07:36
Picon
Picon

Re: Whats up with the make process?

Harry Putnam <reader <at> newsguy.com> writes:

> As is often the case with man pages, `man autoconf' is written for
> someone who understands at least %75 percent of what is expected and
> what will happen and has experience already with the program.

In Debian, you could 'apt-get install autobook' to get more comprehensive
(and maybe also comprehensible?) documentation.  The autobook home is at
http://sources.redhat.com/autobook/autobook/autobook.html, I believe.

HTH,
  Colin
Permalink | Reply | 2 comments |

Gmane