Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python 2.0 compile fails on mandrake 8 #34427

Closed
lkcl mannequin opened this issue Apr 27, 2001 · 4 comments
Closed

python 2.0 compile fails on mandrake 8 #34427

lkcl mannequin opened this issue Apr 27, 2001 · 4 comments
Assignees
Labels
build The build process and cross-build

Comments

@lkcl
Copy link
Mannequin

lkcl mannequin commented Apr 27, 2001

BPO 419462
Nosy @akuchling

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = 'https://github.com/akuchling'
closed_at = <Date 2001-07-14.21:02:29.000>
created_at = <Date 2001-04-27.12:08:01.000>
labels = ['build']
title = 'python 2.0 compile fails on mandrake 8'
updated_at = <Date 2001-07-14.21:02:29.000>
user = 'https://bugs.python.org/lkcl'

bugs.python.org fields:

activity = <Date 2001-07-14.21:02:29.000>
actor = 'akuchling'
assignee = 'akuchling'
closed = True
closed_date = None
closer = None
components = ['Build']
creation = <Date 2001-04-27.12:08:01.000>
creator = 'lkcl'
dependencies = []
files = []
hgrepos = []
issue_num = 419462
keywords = []
message_count = 4.0
messages = ['4552', '4553', '4554', '4555']
nosy_count = 3.0
nosy_names = ['jhylton', 'akuchling', 'lkcl']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue419462'
versions = []

@lkcl
Copy link
Mannequin Author

lkcl mannequin commented Apr 27, 2001

bddbmodule fails to compile on mandrake 8.

if bdb is not a mandatory module, autoconf should be
used to
detect that bdb is or is not installed. [it's looking
for
R_NEXT etc. which don't exist]

@lkcl lkcl mannequin closed this as completed Apr 27, 2001
@lkcl lkcl mannequin assigned akuchling Apr 27, 2001
@lkcl lkcl mannequin added the build The build process and cross-build label Apr 27, 2001
@lkcl lkcl mannequin closed this as completed Apr 27, 2001
@lkcl lkcl mannequin assigned akuchling Apr 27, 2001
@lkcl lkcl mannequin added the build The build process and cross-build label Apr 27, 2001
@lkcl
Copy link
Mannequin Author

lkcl mannequin commented May 4, 2001

Logged In: YES
user_id=80200

update: there is an option in the Modules setup which can be
used to explicity disable bddb. however, this, i feel,
should be totally unnecessary.

why exactly, is autoconf used, when it cannot be told -
correctly -
not to use bddb? i attempted a compile with --without-bddb
(or
whatever it was), and it still failed. because there just
_happens_
to be a db.h file _somewhere_ on the system, the configure
test "assumes" that there is a valid bddb somewhere, which
there isn't.

@jhylton
Copy link
Mannequin

jhylton mannequin commented May 9, 2001

Logged In: YES
user_id=31392

I wonder if the builtin bsddb module should be deprecated.
The fact
that it gets built causes a fair bit of trouble for users of
bsddb3,
which I assume is the preferred interface.

@akuchling
Copy link
Member

Logged In: YES
user_id=11375

Autoconf no longer mucks around with BSDDB at all; it was
ripped out for Python 2.1, so this bug can be closed, to
be replaced by a multitude of setup.py bugs.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build The build process and cross-build
Projects
None yet
Development

No branches or pull requests

1 participant