From: Adam Thompson <arthompson1990@gmail.com>
To: Charles Hallenbeck <chuckh@ftml.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] debian and redhat
Date: Tue, 15 Apr 2014 14:32:22 +0100 [thread overview]
Message-ID: <20140415133222.GM7901@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <alpine.LNX.2.03.1404150707160.1240@ftml.net>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Tue, Apr 15, 2014 at 07:10:18AM -0400, Charles Hallenbeck wrote:
> I just noticed that on my archlinux system, the default js library is js24, and so I tried an experiment. In the src
> directoryh of edbrowse, I did a make clean, then make, and it compiled and linked without any complaints. I think that's
> cool! I had also just done a git pull, so it's the latest 3.5.1 source I'm using.
That's good to hear. At least we can be fairly sure it's not something we're doing.
The only thing I can think of is that it's a Debian-specific patch or specific
build flags which don't match how we're building edbrowse,
however until we know more about how the debian package is built it's just
speculation.
As a long-time Debian user it's a shame for me that I can't just build against
the packaged version of mozjs. It's also slightly strange that Debian has a
(broken) mozjs 26 package as well. I'm not sure what this is based on but I'd
quite like to find out.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-04-15 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 5:45 Karl Dahlke
2014-04-15 11:10 ` Charles Hallenbeck
2014-04-15 13:32 ` Adam Thompson [this message]
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=20140415133222.GM7901@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chuckh@ftml.net \
/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).