Hi list.
I'd like to fix an error and take the bounty.
https://www.bountysource.com/issues/28271221-bounty-for-fixing-aw-snap-
pages-on-freebsd-10-2
I used to be interested in the issue but only now when exams is over I
have some time/enough time.
Is anyone working on this? Could I fix this, sen
I've just fixed the Aw, snap. I believe so.
The patch is going to be huge, not because of this simple bug. New
version was ported as well with some extra things. I need few more days
to polish everything and create patches for some things that are to
ugly now. And probably few days more to be sure
On Thu, 2016-08-18 at 05:09 +0300, clutton wrote:
> I've just fixed the Aw, snap. I believe so.
>
> The patch is going to be huge, not because of this simple bug. New
> version was ported as well with some extra things. I need few more
> days
> to polish everything and
On Sat, 2016-08-20 at 21:58 +0300, Arto Pekkanen wrote:
> You are so AWESOME!!! :) Thank you very much for your efforts!
>
Nono, I'm not awesome. I still haven't finished the whole thing.
You can tell something like that when it'll be done.
signature.asc
Description: This is a digitally signed m
On Thu, 2016-08-18 at 05:09 +0300, clutton wrote:
> I've just fixed the Aw, snap. I believe so.
Ok, time to admit the defeat. I haven't fixed the issue in time, and I
planned to do so till the summer is there. Being to much arrogant I
started just before the end of time. I still ca
chrome work according to a plan, I don't think
that they would add another OS. Unless there are a lot of people
interested.
About Linuxism, - they divide code very simple, if you don't like the
functionality, you can rewrite it for your OS... The thing is - we use
a lot of code written f
On Wed, 2016-09-14 at 13:59 -0700, Yuri wrote:
> Gif from the zip attachment here
> https://bugzilla.mozilla.org/show_bug.cgi?id=497787 crashes chrome
> 51.0.2704.84 every single time.
Consider updating your chromium.
signature.asc
Description: This is a digitally signed message part
On Mon, 2016-09-19 at 10:28 +, bugzilla-nore...@freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
>
> bk...@cs.ucl.ac.uk changed:
>
It's not simple to fix because good hardware is required to do the
debugging. Ideally > 64G of ram. Then I could have everything in
On Sun, 2016-10-02 at 10:50 -0600, drhowarddrf...@charter.net wrote:
> A while back, I updated devel/icu to version 57, but chromium
> requires
> version 55. Updating Chromium fails due to software vulnerabilities
> and now I can't run chromium at all.
There is a message. Update your chromium with
On Sun, 2016-10-02 at 14:40 -0600, drhowarddrf...@charter.net wrote:
> Yes but then I'm running with a long list of vulnerabilities. Come to
> think of it, do I care? I really didn't look into whether it's a big
> concern or not.
Well, then you should have being complained on outdated port not the
I've started porting 54 version of chrome.
7823 left to build before new complications would be met :)
If you want to help in any way, let me know.
I'm writing mainly because if someone would work on the this task,
let's cooperate.
signature.asc
Description: This is a digitally signed message pa
On Fri, 2016-10-14 at 06:42 +0300, clutton wrote:
> I've started porting 54 version of chrome.
>
> 7823 left to build before new complications would be met :)
> If you want to help in any way, let me know.
>
> I'm writing mainly because if someone would work on the
On Sun, 2016-10-16 at 20:40 +0200, René Ladan wrote:
> Forwarding a compilation failure with clang 3.9.0 which is currently
> being tested in FreeeBSD 12.
[snip]
Everything works without this. clang39 is mandatory for new chromium
54, well it can be compiled with more older but chromium build syst
On Sat, 2016-10-15 at 22:58 +0300, clutton wrote:
> On Fri, 2016-10-14 at 06:42 +0300, clutton wrote:
Just fixed one major issue. Those user observers left, it would compile
and work if two strings was commented but I would prefer to make
appropriate patch, without cutting unknown.
ht
On Sun, 2016-10-16 at 20:40 +0200, René Ladan wrote:
> Forwarding a compilation failure with clang 3.9.0 which is currently
> being tested in FreeeBSD 12.
>
> René
Oh, I was wrong... What I was thinking as an UserActivityObserverPtr
problem appears to be trivial_pair_copy problem. Chrome 54 needs
On Mon, 2016-10-17 at 01:42 +0300, clutton wrote:
> On Sat, 2016-10-15 at 22:58 +0300, clutton wrote:
Old bugs are preserved because someone might like them :)
Everything works like before, just new version and new build system.
Shall we commit this to main tree or wait some time more and try
On Fri, 2016-11-18 at 23:43 -0800, Ori Bernstein wrote:
> Working around it for the sake of the build by removing the extern on
> environ
> (even though I'm almost entirely certian that it won't work correctly
> in the
> final version, I get the missing '-lexecinfo' that I initially ran
> into
> in
On Fri, 2016-11-18 at 23:43 -0800, Ori Bernstein wrote:
>
> Buy I don't see anything in either linker flags or the wrapper
> scripts that
> would lead to -Wl,-no-undefined getting passed down here. Does lld
> behave
> differently than gnu ld? I noticed that we seem to be using it now,
> no idea
>
On Sat, 2016-11-26 at 06:21 -0500, Stari Karp wrote:
> web browser, please?
>
> Dear Sir,
>
> I did "play" to build a web browser https://iridiumbrowser.de/
> There are also some on https://forums.freebsd.org/threads/58611/
>
> but I do not have any success. I hope that OpenBSD settings will hel
On Fri, 2016-12-02 at 11:32 -0800, Yuri wrote:
> The message is:
>
> /usr/bin/ld: cannot find -ldl
> c++: error: linker command failed with exit code 1 (use -v to see
> invocation)
>
>
> Yuri
Somewhere dl hasn't being removed. Post more verbose output. What you
did, etc.
signature.asc
Descrip
On Sat, 2016-12-03 at 00:55 -0800, Yuri wrote:
> OPTIONS_SET= PULSEAUDIO SOUND WEBRTC IPV6 THREADED_RESOLVER
> THREADS
Post full output. pastebin would do.
signature.asc
Description: This is a digitally signed message part
On Sat, 2016-12-03 at 13:10 -0800, Yuri wrote:
> On 12/03/2016 07:32, clutton wrote:
> >
> > Post full output. pastebin would do.
>
> http://pastebin.com/BCPzJAfV
>
>
> Yuri
>
https://www.youtube.com/watch?v=eT9K0TAfiIQ&t=1168
This is weird, you shouldn&
On Mon, 2016-12-05 at 11:30 -0800, Yuri wrote:
> On 12/03/2016 13:31, Ori Bernstein wrote:
> >
> > This seems to be an error in building llvm, not in building
> > chromium.
> >
> > Stop.
> > make[3]: stopped in /usr/ports/devel/llvm39
> > *** Error code 1
>
> llvm maintainer says tha
On Mon, 2016-12-05 at 13:43 -0800, Yuri wrote:
> On 12/05/2016 12:35, clutton wrote:
> >
> > Can you build devel/llvm39 without chromium successfully?
>
> The standalone llvm39 build fails with the same message.
>
>
> Yuri
Ok, no a chromium fault then.
signat
On Sat, 2016-12-10 at 14:03 -0800, Cy Schubert wrote:
> The hackish patch to address this and a subsequent break is:
>
> Index: /usr/ports/www/chromium/Makefile
> ===
> --- /usr/ports/www/chromium/Makefile(revision 428271)
> +++ /
25 matches
Mail list logo
