From: Kevin Carhart <kevin@carhart.net>
To: Adam Thompson <arthompson1990@gmail.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] about compiling 3.5.1
Date: Tue, 24 Jun 2014 18:48:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1406241746170.16740@carhart.net> (raw)
In-Reply-To: <20140624140224.GV5577@toaster.adamthompson.me.uk>
Hi Adam,
> Wow, that's quite an old version now.
> Out of interest, what version of CentOS were you trying to use,
> and is there any way to get edbrowse to compile there or is it simply not
> possible without massive amounts of compilation (e.g. new Python etc)?
Ok, there are actually 3 boxes altogether. The first is carhart.net,
which my brother runs and I have an account. That's where I have tinkered
with 3.3.1. and learned a ton. But I moved away from it because I don't
have root access, can't install packages and have to give alternate paths
for everything. The information for carhart.net is:
[kevin@carhart ~]$ cat /etc/redhat-release
CentOS release 5.10 (Final)
[kevin@carhart ~]$ rpm -q centos-release
centos-release-5-10.el5.centos
[kevin@carhart ~]$ uname -rmi
2.6.18-371.9.1.el5.centos.plus i686 i386
Then I wanted to learn more linux and be able to stretch out, and have
someplace to run long HTTP-scripting jobs that are my weird career. So I
went to vpslink.com and have had a 32-bit CentOS for the past five
years. It may be considered really old! I don't know what's going on
with the installation but would be happy to go into more detail or try
some commands and report on the output if it tells us something that can
generalize to others. Here is the information about the system:
[root@crispi-gosh ~]# cat /etc/redhat-release
CentOS release 5.4 (Final)
[root@crispi-gosh ~]# rpm -q centos-release
centos-release-5-4.el5.centos.1
[root@crispi-gosh ~]# uname -rmi
2.6.18-128.7.1.el5xen i686 i386
[root@crispi-gosh ~]#
Box #3 - The Debian:
The Debian where I got 3.5.1 to compile is just a couple of days old and
is fresh out of linode.com. It's very generic, I barely made any
decisions. Here's what it tells me about this one:
My Debian 7.5 Profile (Latest 64 bit (3.14.5-x86_64-linode42))
3.14.5-x86_64-linode42 x86_64 unknown
> How am I finding 3.5.1 so far?
It's a pleasure, as usual. I am excited to play along and learn what the
new parentNode and event code is doing and ask some questions. Thanks
to the developers for all of this work!
Kevin
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2014-06-25 1:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 22:54 [Edbrowse-dev] jQuery Karl Dahlke
2014-05-09 0:57 ` Kevin Carhart
2014-06-21 9:43 ` [Edbrowse-dev] about compiling 3.5.1 Kevin Carhart
2014-06-21 9:58 ` Charles Hallenbeck
2014-06-21 22:15 ` Kevin Carhart
2014-06-21 23:03 ` Chris Brannon
2014-06-22 16:41 ` Adam Thompson
2014-06-22 23:39 ` Kevin Carhart
2014-06-24 14:02 ` Adam Thompson
2014-06-25 1:48 ` Kevin Carhart [this message]
2014-06-25 18:34 ` Adam Thompson
2014-06-25 23:44 ` Kevin Carhart
2014-06-26 9:53 ` Kevin Carhart
2014-06-24 14:09 Karl Dahlke
2014-06-24 18:11 ` Chris Brannon
2014-06-25 18:40 ` Adam Thompson
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=alpine.LRH.2.03.1406241746170.16740@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=arthompson1990@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 NNTP newsgroup(s).