Skip to content

LD_LIBRARY_PATH having more than one colon separated component raises LookupError line 305 debug.py #202

@bootchk

Description

@bootchk

So LD_LIBRARY_PATH, if set, should only be one path, because the code assumes that.

This surprised me because more generally (for the linking loader) LD_LIBRARY_PATH can be a colon separated list of paths.
Why I set LD_LIBRARY_PATH in the first place? No good reason, just that some other build in my container required it, since Ubuntu installs user built libraries to non-standard place?

I suppose you could change the document to say "only set LD_LIBRARY_PATH, to one path, if the library for which you are generating documents is not in a standard installed place."

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions