unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: David Larsson <david.larsson@selfhosted.xyz>, 32087@debbugs.gnu.org
Subject: bug#32087: gcc -m32 can't find stubs-32.h
Date: Tue, 10 Jul 2018 19:40:24 +0200	[thread overview]
Message-ID: <8736wrq99z.fsf@gnu.org> (raw)
In-Reply-To: <87r2kbmb51.fsf@lassieur.org> ("Clément Lassieur"'s message of "Tue, 10 Jul 2018 16:13:46 +0200")

Hello,

Clément Lassieur <clement@lassieur.org> skribis:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Clément Lassieur <clement@lassieur.org> writes:
>>
>>> Ricardo Wurmus <rekado@elephly.net> writes:
>>>
>>>> David Larsson <david.larsson@selfhosted.xyz> writes:
>>>>
>>>>> I tried to run gcc to compile a simple c program which fails:
>>>>
>>>> Are you using the “gcc-toolchain” package?
>>>
>>> I reproduce that bug with gcc-toolchain.
>>
>> If you’re trying to compile for i686, should you not be using the i686
>> variant of gcc-toolchain?  You can build it with
>>
>>     guix build --system=i686-linux gcc-toolchain
>
> How would you install that variant?

Currently you’d have to do:

  guix package -i `guix build -s i686-linux gcc-toolchain`

which is not ideal.

>> (I don’t really know much about this, but we don’t build GCC with
>> multilib support.)
>
> This option is in the gcc manual that we package, so I think it should
> be supported.

Yeah.  The problem is that currently we don’t build glibc with multilib
support.  Something for the next ‘core-updates’ cycle if you feel like
working on it!  :-)

Ludo’.

  reply	other threads:[~2018-07-10 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-07 18:55 bug#32087: gcc -m32 can't find stubs-32.h David Larsson
2018-07-10 11:21 ` Ricardo Wurmus
2018-07-10 11:45   ` Clément Lassieur
2018-07-10 13:40     ` Ricardo Wurmus
2018-07-10 14:13       ` Clément Lassieur
2018-07-10 17:40         ` Ludovic Courtès [this message]
2018-07-10 19:54           ` Clément Lassieur

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736wrq99z.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32087@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=david.larsson@selfhosted.xyz \
    /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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).