25 Kasım 2016 Cuma 00:49:58 UTC+2 tarihinde Ralph Giles yazdı:
> tl;dr This is a heads-up that all gecko developers should install rust.
>
> Next week I plan to switch our default build config to require Rust
> when building Firefox.[1] If you compile Firefox from the C++ source,
> please install
On Thu, Nov 24, 2016 at 2:49 PM, Ralph Giles wrote:
> You'll still be able to build without a rust compiler by adding:
>
> ac_add_options --disable-rust
Just a heads up that I've removed this configure option in bug
1284816, so this will stop working on mozilla-central with the next
autoland m
On Wed, Dec 21, 2016, at 04:56 PM, Julian Seward wrote:
> On 21/12/16 07:55, Jim Blandy wrote:
> > The only things I really want anyway are:
> >
> > mk_add_options MOZ_OBJDIR=obj-bug
> > ac_add_options --enable-debug='-g3 -O0 -fno-inline'
> > ac_add_options --disable-optimize
>
> As a side note,
On 21/12/16 07:55, Jim Blandy wrote:
> The only things I really want anyway are:
>
> mk_add_options MOZ_OBJDIR=obj-bug
> ac_add_options --enable-debug='-g3 -O0 -fno-inline'
> ac_add_options --disable-optimize
As a side note, I tend to use "-Og -g" as that gives much faster code
than -O0 whilst re
On Wed, Dec 21, 2016 at 12:41:37AM -0600, J. Ryan Stinnett wrote:
> On Wed, Dec 21, 2016 at 12:23 AM, Jim Blandy
> wrote:
> > I had a .mozconfig file that included the line:
> >
> > . "$topsrcdir/build/mozconfig.common"
>
> My understanding is that we're generally not supposed to include the
> in
All the more reason for "mach" to be the exclusive place to put all these
smarts.
The only things I really want anyway are:
mk_add_options MOZ_OBJDIR=obj-bug
ac_add_options --enable-debug='-g3 -O0 -fno-inline'
ac_add_options --disable-optimize
On Tue, Dec 20, 2016 at 10:41 PM, J. Ryan Stinnett
On Wed, Dec 21, 2016 at 12:23 AM, Jim Blandy wrote:
> I had a .mozconfig file that included the line:
>
> . "$topsrcdir/build/mozconfig.common"
My understanding is that we're generally not supposed to include the
in-tree mozconfigs in our local builds, since they are free to make
various automati
I had a .mozconfig file that included the line:
. "$topsrcdir/build/mozconfig.common"
This turns out to cause problems: it loads build/mozconfig.rust, which says
to look for rustc in $topsrcdir/rustc/bin, leading to errors like this:
0:05.53 checking for rustc... not found
0:05.53 DEBUG: rustc
On 16/12/16 19:26, Ralph Giles wrote:
Anyway, thanks for the suggestion, Simon. I filed
https://bugzil.la/1324040 with this fix.
In the meantime, the curl command line from https://rustup.rs/ should
work equivalently.
Oops, I wrote this earlier and forgot to click Send.
--
http://docs.python
Anyway, thanks for the suggestion, Simon. I filed
https://bugzil.la/1324040 with this fix.
In the meantime, the curl command line from https://rustup.rs/ should
work equivalently.
-r
On Fri, Dec 16, 2016 at 9:40 AM, Ralph Giles wrote:
> On Fri, Dec 16, 2016 at 9:19 AM, Simon Sapin wrote:
>
>>
On Fri, Dec 16, 2016 at 9:19 AM, Simon Sapin wrote:
> RUSTUP_URL_BASE = 'https://static-rust-lang-org.s3.amazonaws.com/rustup'
>
> If that fixes the issue for you, it’s likely that your Python version does
> not support SSL SNI.
I can reproduce with python urlib2.urlopen() on an ubuntu 14.04
On 16/12/16 17:27, Ben Kelly wrote:
I tried ./mach bootstrap on a fresh m-c this morning and got:
Will try to install Rust.
Downloading rustup-init... Error running mach:
['bootstrap']
The error occurred in code that was called by the mach command. This is
either
a bug in the called code i
I tried ./mach bootstrap on a fresh m-c this morning and got:
Will try to install Rust.
Downloading rustup-init... Error running mach:
['bootstrap']
The error occurred in code that was called by the mach command. This is
either
a bug in the called code itself or in the way that mach is calli
Today we've pushed the change to enable rust language code by default
in Firefox builds. The changes are on the autoland branch right now,
so this will affect your builds from mozilla-central or gecko-dev
starting tomorrow. This brings our default developer build in line
with what we've been doing
I wasn't able to enable Rust by default this week. While it's working
for most developers, there are some automation jobs which aren't ready
for the change. We'll address those and continue to improve the
`./mach boostrap` installer behaviour before flipping the switch.
Thanks to everyone for your
On Mon, Nov 28, 2016 at 12:01:45PM -0800, Gerald Squelart wrote:
> On Tuesday, November 29, 2016 at 5:03:17 AM UTC+11, Gregory Szorc wrote:
> > > On Nov 27, 2016, at 14:46, Gerald Squelart wrote:
> > >
> > >> On Saturday, November 26, 2016 at 3:59:05 AM UTC+11, Ralph Giles wrote:
> > >> On Fri, No
See inline.
> On Nov 28, 2016, at 11:37 AM, Ralph Giles wrote:
>
> On Mon, Nov 28, 2016 at 9:28 AM, Michael Froman wrote:
>
>> Any thoughts? Further info:
>> mfroman-23602:moz-central mfroman$ which rustc
>> /Users/mfroman/.cargo/bin/rustc
>> mfroman-23602:moz-central mfroman$ rustc --version
On Tuesday, November 29, 2016 at 5:03:17 AM UTC+11, Gregory Szorc wrote:
> > On Nov 27, 2016, at 14:46, Gerald Squelart wrote:
> >
> >> On Saturday, November 26, 2016 at 3:59:05 AM UTC+11, Ralph Giles wrote:
> >> On Fri, Nov 25, 2016 at 7:48 AM, Andrew Halberstadt
> >> wrote:
> >>
> >>> For anyon
> On Nov 27, 2016, at 14:46, Gerald Squelart wrote:
>
>> On Saturday, November 26, 2016 at 3:59:05 AM UTC+11, Ralph Giles wrote:
>> On Fri, Nov 25, 2016 at 7:48 AM, Andrew Halberstadt
>> wrote:
>>
>>> For anyone confused by this, the binaries are downloaded to ~/.cargo/bin
>>> and adding this dir
On Mon, Nov 28, 2016 at 9:28 AM, Michael Froman wrote:
> Any thoughts? Further info:
> mfroman-23602:moz-central mfroman$ which rustc
> /Users/mfroman/.cargo/bin/rustc
> mfroman-23602:moz-central mfroman$ rustc --version
> error: no default toolchain configured
Very mysterious. This error messa
I tried the bootstrap on OS X (after a fresh pull from mozilla-central this
morning), and I also have failures. I’ve added the following lines to my
.profile:
export PATH="$HOME/.cargo/bin:$PATH"
source /Users/mfroman/.cargo/env
I continue to get errors from the bootstrap process:
The details o
On Sun, Nov 27, 2016 at 2:46 PM, Gerald Squelart wrote:
> Following your instructions, rustc and friends are in ~/.cargo/bin, and I've
> added that path in my $PATH.
>
> But now, `./mach build` gives me:
> force-cargo-build
> env: /usr/local/bin/cargo: No such file or directory
> [...]
> Sym
On Saturday, November 26, 2016 at 3:59:05 AM UTC+11, Ralph Giles wrote:
> On Fri, Nov 25, 2016 at 7:48 AM, Andrew Halberstadt
> wrote:
>
> > For anyone confused by this, the binaries are downloaded to ~/.cargo/bin
> > and adding this directory to your $PATH should fix the issue. The
> > bootstrap
On Fri, Nov 25, 2016 at 7:48 AM, Andrew Halberstadt
wrote:
> For anyone confused by this, the binaries are downloaded to ~/.cargo/bin
> and adding this directory to your $PATH should fix the issue. The
> bootstrapper explains this if you run it a second time, but makes no
> mention of it the firs
When first installing rust with ./mach bootstrap the install is
successful, but there is a message about not being able to find the
compiler immediately afterwards.
For anyone confused by this, the binaries are downloaded to ~/.cargo/bin
and adding this directory to your $PATH should fix the issu
25 matches
Mail list logo
