From: Linpeng Tang <chnttlp@gmail.com>
To: gentoo-alt <gentoo-alt@lists.gentoo.org>
Subject: Re: [gentoo-alt] problems with bootstrapping in Gentoo-prefix
Date: Sat, 26 Jan 2013 01:25:12 -0500 [thread overview]
Message-ID: <CAL_rV8UApoFMMJQ4Dnn-NfvxyUKZeDUTAH0PXB_FsZL071FS5Q@mail.gmail.com> (raw)
In-Reply-To: <87zjzxy7vb.fsf@proton.in.awa.tohoku.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
Benda,
Thanks for all the help! The installation now finishes normally. I expect
Gentoo-prefix will become a handy tool for using the university cluster
machines.
Best.
2013/1/25 heroxbd <heroxbd@gmail.com>
> Hi Linpeng,
>
> For openssh, your glibc is too old to support FORTIFY. Therefore I have
> the following in my
> $EPREFIX/etc/portage/package.mask
>
> # from this version _FORTIFY_SOURCE=2 is enabled by default.
> # fails on glibc-2.{4,5}
> >=net-misc/openssh-6.0
>
> because from openssh-6 its configure system false identifies fortify
> feature.
>
> This is just a work around.
>
> Cheers,
> Benda
>
>
--
-----------------------------------
Princeton University
Computer Science Department
Linpeng Tang
[-- Attachment #2: Type: text/html, Size: 1227 bytes --]
next prev parent reply other threads:[~2013-01-26 6:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 22:12 [gentoo-alt] problems with bootstrapping in Gentoo-prefix Linpeng Tang
2013-01-19 22:28 ` [gentoo-alt] " Linpeng Tang
2013-01-21 7:35 ` heroxbd
2013-01-21 8:31 ` [gentoo-alt] " Christopher Schwan
2013-01-21 15:18 ` Linpeng Tang
2013-01-22 3:12 ` Linpeng Tang
2013-01-22 7:19 ` heroxbd
2013-01-22 22:19 ` Fabian Groffen
2013-01-23 14:32 ` Linpeng Tang
2013-01-24 0:51 ` Linpeng Tang
2013-01-24 4:41 ` heroxbd
2013-01-25 8:39 ` heroxbd
2013-01-26 6:25 ` Linpeng Tang [this message]
2013-01-26 11:29 ` heroxbd
2013-02-01 6:57 ` Linpeng Tang
2013-02-01 17:47 ` Steven Trogdon
2013-02-02 12:37 ` Fabian Groffen
2013-02-02 14:41 ` Linpeng Tang
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=CAL_rV8UApoFMMJQ4Dnn-NfvxyUKZeDUTAH0PXB_FsZL071FS5Q@mail.gmail.com \
--to=chnttlp@gmail.com \
--cc=gentoo-alt@lists.gentoo.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