The symbols missing seem to be from libncurses. Probably installing
ncurses would fix it, though I find funny that LLVM links to it. Shrug.
I guess we should update the dependencies section, please confirm if
installing ncurses worked and I'll do it (or send a PR directly, which
would be great! :)
The full output is attached here.
On Sat, Mar 18, 2017 at 2:28 PM, Josh Matthews
wrote:
> On 2017-03-18 4:04 AM, Spinet wrote:
>
>> Hi, I was facing the same difficulty when I tried to build servo as per
>> the instructions on github. I tried clearing and building again but I'm
>> getting the er
Last lines:
thread 'main' panicked at 'failed with: exit code: 2',
/home/sagartoms/servo/.cargo/git/checkouts/osmesa-src-bf84ce2b80210dd7/42509fb/build.rs:52
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[Warning] Could not generate notification! Optional Python module 'dbus' is not
instal
On 2017-03-18 4:04 AM, Spinet wrote:
Hi, I was facing the same difficulty when I tried to build servo as per the instructions on github.
I tried clearing and building again but I'm getting the error "Optional Python module 'dbus'
is not installed" although I had tried building servo after insta
Hi, I was facing the same difficulty when I tried to build servo as per the
instructions on github. I tried clearing and building again but I'm getting the
error "Optional Python module 'dbus' is not installed" although I had tried
building servo after installing dbus by "sudo apt-get install py
Awesome! Glad it worked out. Welcome to the bleeding edge :)
jack.
On Fri, Mar 17, 2017 at 3:48 PM, wrote:
> On Friday, March 17, 2017 at 2:31:49 PM UTC-4, Jack Moffitt wrote:
>> I suspect something got messed up in a previous aborted build. Please
>> try mach clean and rebuilding.
>>
>> jack.
On Friday, March 17, 2017 at 2:31:49 PM UTC-4, Jack Moffitt wrote:
> I suspect something got messed up in a previous aborted build. Please
> try mach clean and rebuilding.
>
> jack.
>
> On Fri, Mar 17, 2017 at 12:11 PM, wrote:
> > On Friday, March 17, 2017 at 12:59:19 PM UTC-4, Jack Moffitt wro
I suspect something got messed up in a previous aborted build. Please
try mach clean and rebuilding.
jack.
On Fri, Mar 17, 2017 at 12:11 PM, wrote:
> On Friday, March 17, 2017 at 12:59:19 PM UTC-4, Jack Moffitt wrote:
>> At the terminal if you type "pip" does it print out the help text or
>> do
On Friday, March 17, 2017 at 12:59:19 PM UTC-4, Jack Moffitt wrote:
> At the terminal if you type "pip" does it print out the help text or
> does it say command not found? Servo is expecting this to be in your
> PATH.
>
> jack.
>
> On Fri, Mar 17, 2017 at 10:54 AM, wrote:
> > On Friday, March 1
At the terminal if you type "pip" does it print out the help text or
does it say command not found? Servo is expecting this to be in your
PATH.
jack.
On Fri, Mar 17, 2017 at 10:54 AM, wrote:
> On Friday, March 17, 2017 at 12:40:52 PM UTC-4, Emilio Cobos Álvarez wrote:
>> Seems like you don't ha
On Friday, March 17, 2017 at 12:40:52 PM UTC-4, Emilio Cobos Álvarez wrote:
> Seems like you don't have pip installed, have you followed all the steps
> in the README to install the required dependencies?
>
> -- Emilio
>
> On Fri, Mar 17, 2017 at 09:31:26AM -0700, ssriv...@ncsu.edu wrote:
> > I
I also saw that error happen with a hosed virtualenv (because of the
hardcoded paths in the virtualenv scripts). In this case, just run `rm
-rf python/_virtualenv` and restart your build.
Fabrice
On 03/17/2017 09:40 AM, Emilio Cobos Álvarez wrote:
Seems like you don't have pip instal
Seems like you don't have pip installed, have you followed all the steps
in the README to install the required dependencies?
-- Emilio
On Fri, Mar 17, 2017 at 09:31:26AM -0700, ssriv...@ncsu.edu wrote:
> I have pulled the latest code from servo github repository and I am using the
> following c
13 matches
Mail list logo
