From: Don Lunder <speedy@carboncode.com>
To: barretp@mcmail.cis.McMaster.CA, linuxppc-dev@lists.linuxppc.org
Subject: Re: postgresql6.5 (and 6.4) type oid problems
Date: Thu, 15 Jul 1999 16:03:08 -0700 [thread overview]
Message-ID: <199907151956.NAA17646@carboncode.com> (raw)
In-Reply-To: <Pine.SOL.3.96.990715171332.22486B-100000@ mcmail.cis.McMaster.CA>
There is something in the powerpc template, that has options that shouldn't
be there, I think that only -00 is suppose to be used, I saw something on
the mailing lists at postgresql.org, about just this thing, and its an
error in the optimizatioin flags.
Altho, I havn't gotten to try this, or make an rpm, but if some one
could... :)
Don Lunder
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
parent reply other threads:[~1999-07-15 23:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.SOL.3.96.990715171332.22486B-100000@ mcmail.cis.McMaster.CA>]
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=199907151956.NAA17646@carboncode.com \
--to=speedy@carboncode.com \
--cc=barretp@mcmail.cis.McMaster.CA \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).