all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nikolai Merinov <nikolai.merinov@member.fsf.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 29522@debbugs.gnu.org, 29555@debbugs.gnu.org
Subject: bug#29522: [bug#29555] [PATCH] gnu: rust: update rust to 1.22.1 and cargo to 1.23.0
Date: Mon, 04 Dec 2017 19:54:13 +0500	[thread overview]
Message-ID: <558D9F77-E950-4D77-86A3-4B633C0E2009@member.fsf.org> (raw)
In-Reply-To: <CAPsKtf+Af4PhX7tzd0uyv9ngMcGysuT7MXALbAh+b-TqB3qEAw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

I added "-lstdc++" to rust standard lib to overcome issue. Which solution is better: 
1. change link flags for rust standard library, or
2. create rust-specific jemalloc as suggested in #29522?

4 декабря 2017 г. 19:33:31 GMT+05:00, Jelle Licht <jlicht@fsfe.org> пишет:
>2017-12-03 20:01 GMT+01:00 Nikolai Merinov
><nikolai.merinov@member.fsf.org>:
>
>> Update for a rustc and cargo packages. This update will also fix a
>> build.
>>
>>
>I do not have enough know-how to properly review your patch, but at
>least I
>can verify it seems to work.
>I was able to build rustc and cargo succesfully with your patches, and
>was
>able to build and run a trivial hello world program written in rust.
>When this patch is merged,  I think we can also close
>http://lists.gnu.org/archive/html/bug-guix/2017-12/msg00006.html, as it
>will no longer be relevant.

-- 
Nikolai Merinov

[-- Attachment #2: Type: text/html, Size: 1610 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Nikolai Merinov <nikolai.merinov@member.fsf.org>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 29522@debbugs.gnu.org, 29555@debbugs.gnu.org
Subject: [bug#29555] [PATCH] gnu: rust: update rust to 1.22.1 and cargo to 1.23.0
Date: Mon, 04 Dec 2017 19:54:13 +0500	[thread overview]
Message-ID: <558D9F77-E950-4D77-86A3-4B633C0E2009@member.fsf.org> (raw)
In-Reply-To: <CAPsKtf+Af4PhX7tzd0uyv9ngMcGysuT7MXALbAh+b-TqB3qEAw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

I added "-lstdc++" to rust standard lib to overcome issue. Which solution is better: 
1. change link flags for rust standard library, or
2. create rust-specific jemalloc as suggested in #29522?

4 декабря 2017 г. 19:33:31 GMT+05:00, Jelle Licht <jlicht@fsfe.org> пишет:
>2017-12-03 20:01 GMT+01:00 Nikolai Merinov
><nikolai.merinov@member.fsf.org>:
>
>> Update for a rustc and cargo packages. This update will also fix a
>> build.
>>
>>
>I do not have enough know-how to properly review your patch, but at
>least I
>can verify it seems to work.
>I was able to build rustc and cargo succesfully with your patches, and
>was
>able to build and run a trivial hello world program written in rust.
>When this patch is merged,  I think we can also close
>http://lists.gnu.org/archive/html/bug-guix/2017-12/msg00006.html, as it
>will no longer be relevant.

-- 
Nikolai Merinov

[-- Attachment #2: Type: text/html, Size: 1610 bytes --]

  reply	other threads:[~2017-12-04 14:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 19:01 [bug#29555] [PATCH] gnu: rust: update rust to 1.22.1 and cargo to 1.23.0 Nikolai Merinov
2017-12-04  7:02 ` ng0
2017-12-04 14:33 ` Jelle Licht
2017-12-04 14:54   ` Nikolai Merinov [this message]
2017-12-04 14:54     ` Nikolai Merinov
2017-12-04 16:05     ` bug#29522: " Danny Milosavljevic
2017-12-04 16:05       ` Danny Milosavljevic
2017-12-05  6:10       ` bug#29522: " Nikolai Merinov
2017-12-09 23:16         ` [bug#29555] [PATCHv3] " Nikolai Merinov
2017-12-10  9:27           ` Danny Milosavljevic
2017-12-10 21:14             ` [bug#29555] [PATCHv4] " Nikolai Merinov

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=558D9F77-E950-4D77-86A3-4B633C0E2009@member.fsf.org \
    --to=nikolai.merinov@member.fsf.org \
    --cc=29522@debbugs.gnu.org \
    --cc=29555@debbugs.gnu.org \
    --cc=jlicht@fsfe.org \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.