[EMAIL PROTECTED] said:
>
> Users' interpretations are mostly wrong (which is why they can't
> figure out
> what's wrong).
> Nice insult.
Don't be silly. It's as true of me as anyone; the difference is that over the
past 30+ years, I've learned to provide (as far as possible) copious detail
On Sun, 04 Feb 2001, John Summerfield wrote:
> [EMAIL PROTECTED] said:
> > I'm afraid I don't understand what you are talking about...unless...
>
> When something doesn't work, if at all possible cut & paste the messages so we
> can see what you can see.
Ya know, I really thought I had put enou
[EMAIL PROTECTED] said:
> Conflicts: glibc < 2.1.90 Is what I removed from the db1 db2 and db3
> SPEC files And here follows the actual attempt at install.
> # rpm -ivh db1-1.85-4.i386.rpm error: failed dependencies:
> glibc < 2.1.90 conflicts with db1-1.85-4
[root@possum /]# rpm -qi
[EMAIL PROTECTED] said:
> I'm afraid I don't understand what you are talking about...unless...
When something doesn't work, if at all possible cut & paste the messages so we
can see what you can see.
Users' interpretations are mostly wrong (which is why they can't figure out
what's wrong).
[EMAIL PROTECTED] said:
> installing package dev-3.1.0-3 needs 3727 inodes on the / filesystem
rm files.
close files
Possibly you need to close some so they go away. Easiest way to accomplish
this is by rebooting (they can be hard to find). This need could arise, for
example, if you updated
On Sun, 04 Feb 2001, you wrote:
> Hello...
> Dan Cyr wrote:
>
> > First off I'll say this. I do not plan on using mysql for transactions.
> > So after reading the following, am I just wasting my time here? Can I just
> > remove the berkeley db requirement from the mysql src.rpms?
>
> Yes. ( and
On Sun, 04 Feb 2001, you wrote:
> [EMAIL PROTECTED] said:
> > Here we go..
> > I took the latest rh7 mysql src.rpm and rebuilt it on rh6.2, but i
> > removed the berkeley db support as it wasn't aparent to me why it was
>
> Precisely what does this mean? You removed buildrequires? Or did you
# rpm -Uvh /usr/src/redhat/RPMS/i686/dev-3.1.0-3.i686.rpm
Preparing...### [100%]
installing package dev-3.1.0-3 needs 3727 inodes on the / filesystem
___
Redhat-devel-list mailing list
[EMAIL PR
Small fix to make python-1.5.2-29.src.rpm to build for i686 arch
Build errors:
Processing files: python-1.5.2-29
File not found: /var/tmp/python/python-root/usr/lib/python1.5/plat-linux-i686
Solution: Change python.spec
Release: 29.1
#Release: 29
%{_prefix}/lib/python1.5/plat-linux-%{_arch}
#%{_
[EMAIL PROTECTED] said:
> The following is from the glibc 2.2 INSTALL file
> `--enable-kernel=VERSION'
> This option is currently only useful on Linux systems. The
> VERSION parameter should have the form X.Y.Z and describes the
> smallest version of the Linux kernel the generate
[EMAIL PROTECTED] said:
> Here we go..
> I took the latest rh7 mysql src.rpm and rebuilt it on rh6.2, but i
> removed the berkeley db support as it wasn't aparent to me why it was
Precisely what does this mean? You removed buildrequires? Or did you change
the configuration?
If you removed
Hello...
Dan Cyr wrote:
> First off I'll say this. I do not plan on using mysql for transactions.
> So after reading the following, am I just wasting my time here? Can I just
> remove the berkeley db requirement from the mysql src.rpms?
>
Yes. ( and the gperf requirement )
I've been doing t
First off I'll say this. I do not plan on using mysql for transactions.
So after reading the following, am I just wasting my time here? Can I just
remove the berkeley db requirement from the mysql src.rpms?
I do like things to be done as they are originally intended (I don't like removing
the be
The following is from the glibc 2.2 INSTALL file
`--enable-kernel=VERSION'
This option is currently only useful on Linux systems. The
VERSION parameter should have the form X.Y.Z and describes the
smallest version of the Linux kernel the generated library is
expected to supp
14 matches
Mail list logo
