Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@systemhalted.org>
To: parisc-linux@lists.parisc-linux.org
Cc: Randolph Chung <tausq@debian.org>
Subject: [parisc-linux] nptl build failures (so close!)
Date: Tue, 26 Jul 2005 15:45:40 -0400	[thread overview]
Message-ID: <20050726194540.GG9703@systemhalted.org> (raw)


Randolph, Dave,

Any thoughts?

../sysdeps/generic/strtol_l.c: In function '____strtol_l_internal':
../sysdeps/generic/strtol_l.c:483: warning: cast discards qualifiers from pointer target type
../sysdeps/generic/strtol_l.c:497: error: 'ERANGE' undeclared (first use in this function)
../sysdeps/generic/strtol_l.c:497: error: (Each undeclared identifier is reported only once
../sysdeps/generic/strtol_l.c:497: error: for each function it appears in.)
../sysdeps/generic/strtol_l.c:517: warning: cast discards qualifiers from pointer target type
../sysdeps/generic/strtol_l.c:520: warning: cast discards qualifiers from pointer target type
make[2]: *** [/mnt/flaire/src/tls-toolchain-hppa/build/glibc-nptl/stdlib/strtol_l.o] Error 1
make[2]: Leaving directory `/mnt/flaire/src/tls-toolchain-hppa/src/glibc/stdlib'
make[1]: *** [stdlib/subdir_lib] Error 2
make[1]: Leaving directory `/mnt/flaire/src/tls-toolchain-hppa/src/glibc'
make: *** [all] Error 2

I tried to debug a weird header file include problem in the nptl headers
last night, but to no avail. It looks like gcc was reordering the includes
and "lll_lock_t" wasn't included. This time around "ERANGE" is missing, but 
if I trace the headers by hand it should have been included.

This looks like an einvironment problem. No other arches seem to define anything
magical to make this work.

I had a similar problem in nptl/descr.h where lowlevellock.h wasn't being
included until after descr.h was entirely processed. Which made no sense
at all.

c.


_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

             reply	other threads:[~2005-07-26 19:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 19:45 Carlos O'Donell [this message]
2005-07-26 21:10 ` [parisc-linux] Re: nptl build failures (so close!) John David Anglin
2005-07-27 16:51   ` Carlos O'Donell

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=20050726194540.GG9703@systemhalted.org \
    --to=carlos@systemhalted.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tausq@debian.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