From: Grant Grundler <grundler@puffin.external.hp.com>
To: amodra@one.net.au
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] xfree86 build problem
Date: Sat, 14 Apr 2001 16:18:47 -0600 [thread overview]
Message-ID: <200104142218.QAA30044@puffin.external.hp.com> (raw)
In-Reply-To: Your message of "Sat, 14 Apr 2001 21:25:57 +0930." <20010414212557.E16364@squeak.one.net.au>
amodra@one.net.au wrote:
> > 2) c++ isn't returning the error reported by collect2
> > Fortunately the build soon dies since the expected product
> > doesn't exist. Known problem?
>
> Are you sure about this statement? It might just be "make" (the presense
> of those `+'s is ringing bells with me but I don't recall the exact
> signifigance.)
I'm not. It might be a make bug.
I've seen make say something like "[ ... ignored ]" when ignoring an error.
Anyway, after spending another two hours on the -fPIC problem, I'm
starting to think the xfree86 lib build is broken by design for __hppa__.
I'll send out another mail with a patch + recipe for building the libs.
I'm pretty close to finding workarounds (not solutions) for the problems.
Do other arches allow non-PIC .o's to be linked into a .so lib?
Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253
next prev parent reply other threads:[~2001-04-14 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 22:21 [parisc-linux] xfree86 build problem Grant Grundler
2001-04-14 11:55 ` amodra
2001-04-14 22:18 ` Grant Grundler [this message]
2001-04-14 23:00 ` Ulrich Drepper
2001-04-14 23:41 ` Alan Cox
2001-04-15 4:23 ` Grant Grundler
2001-04-15 12:32 ` Alan Cox
2001-04-15 4:42 ` amodra
-- strict thread matches above, loose matches on Subject: below --
2001-04-15 6:17 amodra
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=200104142218.QAA30044@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=amodra@one.net.au \
--cc=parisc-linux@parisc-linux.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