edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] debian and redhat
Date: Tue, 15 Apr 2014 05:45:36 +0000	[thread overview]
Message-ID: <20140315054536.eklhad@comcast.net> (raw)

Prompted by Adam's message, I tried an experiment.
I pulled the latest rpm package from Fedora for the js library,
and installed it, and it worked.
Emboldend by this, I pulled down the development package,
installed the headers, rebuilt everything,
now using just the command make rather than make
with a bunch of arguments, and built,
and ran jsrt through its paces, and it worked.

ftp://rpmfind.net
login anonymous
cd /linux/fedora/linux/development/rawhide/i386/os/Packages/m
get mozjs24-24.2.0-3.fc21.i686.rpm
get mozjs24-devel-24.2.0-3.fc21.i686.rpm

Notice it is exactly the same version we are using from source.
So the debian problem is perhaps debian specific,
and not systemic.

At this point I am tempted to remove all the js I built from source,
as it takes up almost 2 gig.

So ... this is an interesting, and I hope helpful, data point.
Edbrowse works on Fedora.
Too bad we haven't convinced redhat to carry edbrowse yet.

Karl Dahlke

             reply	other threads:[~2014-04-15  9:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15  5:45 Karl Dahlke [this message]
2014-04-15 11:10 ` Charles Hallenbeck
2014-04-15 13:32   ` Adam Thompson
2014-04-15 12:48 ` Chris Brannon
2014-04-21 13:13   ` MENGUAL Jean-Philippe
2014-04-22 14:01     ` Adam Thompson
2014-06-06  9:15       ` 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=20140315054536.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.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).