From: Guy fleury <hoonandon@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: need help with gcc -m32
Date: Mon, 8 Apr 2019 15:45:19 +0200 [thread overview]
Message-ID: <CAOYpmvpTB=jN-CP9ZifrQ9O7yFkU8jXDJ9Vsd0_iWXp=7N-xsA@mail.gmail.com> (raw)
In-Reply-To: <87r2acwzv6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Merci beaucoup!
Le 8 avr. 2019 12:33, "Ludovic Courtès" <ludo@gnu.org> a écrit :
> Bonjour,
>
> Guy fleury <hoonandon@gmail.com> skribis:
>
> > How can i built binarie for 32 bits i am on 64 bits.
> > with gcc i get:
> > ---------------------------------------------------------
> > guy@guixSd ~/tuto/c$ gcc -m32 -o hello hello.c
> > In file included from /home/guy/.guix-profile/include/features.h:452,
> > from
> > /home/guy/.guix-profile/include/bits/libc-header-start.h:33,
> > from /home/guy/.guix-profile/include/stdio.h:27,
> > from hello.c:1:
> > /home/guy/.guix-profile/include/gnu/stubs.h:7:11: erreur fatale:
> > gnu/stubs-32.h : Aucun fichier ou dossier de ce type
> > # include <gnu/stubs-32.h>
> > ^~~~~~~~~~~~~~~~
> > compilation terminée.
> > ------------------------------------------------------------
> -------------------------------------------
> >
> > which package to download?
>
> Our GCC toolchain does not support ‘-m32’. Instead, to build a 32-bit
> program on a 64-bit machine, you would do something like:
>
> guix environment --ad-hoc gcc-toolchain -s i686-linux --pure
>
> HTH!
>
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 1712 bytes --]
prev parent reply other threads:[~2019-04-08 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 18:05 need help with gcc -m32 Guy fleury
2019-04-08 10:33 ` Ludovic Courtès
2019-04-08 13:45 ` Guy fleury [this message]
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='CAOYpmvpTB=jN-CP9ZifrQ9O7yFkU8jXDJ9Vsd0_iWXp=7N-xsA@mail.gmail.com' \
--to=hoonandon@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.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.
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).