From: Girish Shilamkar <Girish.Shilamkar@Sun.COM>
To: Ext4 Mailing List <linux-ext4@vger.kernel.org>
Subject: Re: [E2fsprogs] Compile error on RHEL4/ia64
Date: Sat, 26 Jul 2008 23:52:08 +0530 [thread overview]
Message-ID: <1217096528.3293.23.camel@alpha.linsyssoft.com> (raw)
In-Reply-To: <1217095878.3293.22.camel@alpha.linsyssoft.com>
CC to mailing list also ...
On Sat, 2008-07-26 at 23:41 +0530, Girish Shilamkar wrote:
> Hi Ted,
> While building e2fsprogs on ia64/rhel4 the following compile error was
> flagged:
>
> Error messages:
> make[4]: Leaving directory `/cache/build/BUILD/e2fsprogs-1.40.7.sun1/lib/uuid'
> CC clear.c
> CC compare.c
> CC copy.c
> CC gen_uuid.c
> gen_uuid.c: In function `uuid__generate_time':
> gen_uuid.c:493: internal compiler error: in ia64_expand_load_address, at
> config/ia64/ia64.c:1184
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
> Preprocessed source stored into /tmp/ccYkSBN6.out file, please attach this to
> your bugreport.
> make[3]: *** [gen_uuid.o] Error 1
>
> e2fsprogs, if supported, sets TLS to appropriate TLS type, which happens to be
> '__thread' for Linux. And hence THREAD_LOCAL is defined as 'static __thread' in
> uuid_gen.c. But it seems that RHEL4 glibc is incompatible with TLS on ia64,
> though e2fsprogs detected that '__thread' is usable.
>
> Further investigation revealed that, With '-O' option it is ok on all
> (rhel4, rhel5, sles9 & sles10) distros but with optimization
> level >=2(-O2, -O3, ...) the problem occurs on RHEL4.
>
> https://bugzilla.lustre.org/show_bug.cgi?id=15514
> has more details about the tests run to verify the above findings,
> comments # 9 and 10.
>
> Regards,
> Girish
next parent reply other threads:[~2008-07-26 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1217095878.3293.22.camel@alpha.linsyssoft.com>
2008-07-26 18:22 ` Girish Shilamkar [this message]
2008-07-27 11:00 ` [E2fsprogs] Compile error on RHEL4/ia64 Theodore Tso
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=1217096528.3293.23.camel@alpha.linsyssoft.com \
--to=girish.shilamkar@sun.com \
--cc=linux-ext4@vger.kernel.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 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.