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

Building for static linking isn't done correctly #312

Open
brong opened this issue Jan 19, 2009 · 8 comments
Open

Building for static linking isn't done correctly #312

brong opened this issue Jan 19, 2009 · 8 comments
Assignees
Milestone

Comments

@brong
Copy link
Member

brong commented Jan 19, 2009

From: Greg A. Woods
Bugzilla-Id: 3135
Version: 2.1.x
Owner: Alexey Melnikov

@brong
Copy link
Member Author

brong commented Jan 19, 2009

Attachment-Id: 1054
From: Greg A. Woods
Type: text/plain
File: auto+static.patch

fixes for autoconf and automake rules for mostly static builds

@brong
Copy link
Member Author

brong commented Dec 17, 2011

From: Greg A. Woods

I was about to submit patches, but then thought I should search because I had a vague memory of sending something before. Obviously it was so long ago that I'd forgotten the details!

I was poking at the code again today and discovered yet another new problem had crept into the top-level Makefile.am, caused by rev 1.30 (for which I cannot find a corresponding bug report or proper explanation for -- it's bogus so far as I can tell).

There should be no dependency in "plugins" on any product file built in "lib", and at least fot he set of mechanisms I normally enable this is true.

However there very definitely is a dependency in "lib" on products built in the "plugins" directory, at least when building static-linked SASL libraries.

Note that the reasoning for prefering dynamically loadable mechanisms is kind of bogus. Nobody but a hacker would ever try to drop in a new authentication module into a running system and hope for it to work! It might be fine for testing and development work, but for secure prodcution systems anyone thinking straight will want to know exactly how their system can operate and they should be more than happy to install new software entirely and carefuly restart everything if they're going to add or remove something as important as an authentication mechanism.

I'll try and attach new patches to this bug report, but I don't find bugzilla very easy to use, so maybe I'll have to just send them to the list -- check the archives of cyrus-sasl in case there's nothing new here.

@brong
Copy link
Member Author

brong commented Dec 17, 2011

Attachment-Id: 1447
From: Greg A. Woods
Type: text/plain
File: sasl-2.patch

fixes for static linking, etc.

@brong
Copy link
Member Author

brong commented Jun 1, 2012

From: Alexey Melnikov

I will cherry-pick some changes from your patch, but I really dislike one mega-patch which contains unrelated changes. It takes ages to separate them.

@brong
Copy link
Member Author

brong commented Jun 9, 2012

Attachment-Id: 1480
From: Alexey Melnikov
Type: text/plain
File: static.linking.and.stuff.bug.3135.diff.txt

Remaining changes mostly related to static linking

@quanah quanah self-assigned this Aug 20, 2024
@quanah quanah added this to the 2.2.0 milestone Aug 20, 2024
@quanah
Copy link
Contributor

quanah commented Aug 20, 2024

static only builds do not compile

@quanah
Copy link
Contributor

quanah commented Aug 20, 2024

See also #814 but this is a separate issue from what's going on there

@Neustradamus
Copy link
Contributor

Neustradamus commented Jan 9, 2025

@robohack: It has been created by you in 2009, 16 years already!

@aamelnikov: This ticket has been taken by you and you have done 2009 -> 2012 patch versions.

What is the situation in 2025?

It blocks currently a new and important Cyrus-SASL version.

Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants