From: Dorian ROSSE <dorianbrice@hotmail.fr>
To: Florian Weimer <fweimer@redhat.com>
Cc: Dorian ROSSE via Libc-alpha <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: glibc 2.35 release tomorrow (2022-02-02).
Date: Wed, 2 Feb 2022 10:03:24 +0000 [thread overview]
Message-ID: <DB6PR08MB2855DC81DDC820AE94A783AADA279@DB6PR08MB2855.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <87mtj9zjyk.fsf@oldenburg.str.redhat.com>
Also if I create a directory glibc-build and if I run this command line this should build fully :
root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/glibc/build# ./configure
> --prefix=/home/ubuntu/programs/glibc-build && make && make install
I hope this is the truth,
Regards.
Dorian Rosse.
________________________________
From: Florian Weimer <fweimer@redhat.com>
Sent: Wednesday, February 2, 2022 10:38:59 AM
To: Dorian ROSSE <dorianbrice@hotmail.fr>
Cc: Dorian ROSSE via Libc-alpha <libc-alpha@sourceware.org>; Carlos O'Donell <carlos@redhat.com>
Subject: Re: glibc 2.35 release tomorrow (2022-02-02).
* Dorian ROSSE:
> i launch this :
>
> '''root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/glibc/build# ./configure
> --prefix=/home/ubuntu/programs/glibc && make && make install'''
>
> i fall on error following :
>
> '''/usr/bin/install -c -m 644 include/limits.h /home/ubuntu/programs/glibc/include/limits.h
> /usr/bin/install: 'include/limits.h' and '/home/ubuntu/programs/glibc/include/limits.h' are the
> same file
> make[1]: *** [Makerules:1173: /home/ubuntu/programs/glibc/include/limits.h] Error 1
> make[1]: Leaving directory '/home/ubuntu/programs/glibc'
> make: *** [Makefile:12 : install] Erreur 2'''
That's because you have set the --prefix option to the source directory
itself. This is not supported. It has to be a separate directory tree.
Thanks,
Florian
prev parent reply other threads:[~2022-02-02 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 1:15 Carlos O'Donell
2022-02-02 8:06 ` Dorian ROSSE
2022-02-02 8:55 ` Florian Weimer
2022-02-02 9:03 ` Dorian ROSSE
2022-02-02 9:38 ` Florian Weimer
2022-02-02 10:03 ` Dorian ROSSE [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB6PR08MB2855DC81DDC820AE94A783AADA279@DB6PR08MB2855.eurprd08.prod.outlook.com \
--to=dorianbrice@hotmail.fr \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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).