Bug 277448 - devel/git: build fails with DEFAULT_VERSIONS+=ssl=base
Summary: devel/git: build fails with DEFAULT_VERSIONS+=ssl=base
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Renato Botelho
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-03 11:26 UTC by Martin Birgmeier
Modified: 2024-03-23 10:13 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (garga)


Attachments
portmaster log (506.47 KB, text/plain)
2024-03-03 11:26 UTC, Martin Birgmeier
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Birgmeier 2024-03-03 11:26:57 UTC
Created attachment 248894 [details]
portmaster log

Scenario:
- FreeBSD stable/14 i386
- ports latest
- using portmaster to update ports
- updated ruby to new default (3.2)
- have "DEFAULT_VERSIONS+=ssl=base" /etc/make.conf
- recompiling devel/git

Result:
- Build fails

Expected result:
- Portmaster should succeed

The logfile is attached.

The build also fails on amd64 (which also uses DEFAULT_VERSIONS+=ssl=base).

-- Martin
Comment 1 Martin Birgmeier 2024-03-06 18:51:18 UTC
The following sequence succeeds:
- rm -r $WRKDIRPREFIX/ports/devel/git
- cd /usr/ports/devel/git
- make
- portmaster devel/git

The following sequence fails:
- cd $HOME (/root)
- rm -r $WRKDIRPREFIX/ports/devel/git
- portmaster devel/git

The following sequence fails:
- rm -r $WRKDIRPREFIX/ports/devel/git
- cd /usr/ports/devel/git
- portmaster devel/git
Comment 2 Marcin Gryszkalis 2024-03-06 19:02:21 UTC
I can confirm that, devel/git builds properly with `make` but fails with portmaster. DEFAULT_VERSIONS doesn't contain ssl in my case.

So the bug should be re-assigned to ports-mgmt/portmaster.
Comment 3 Marcin Gryszkalis 2024-03-06 23:30:23 UTC
It's fixed in portmaster and Make scripts:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277492
Comment 4 Martin Birgmeier 2024-03-23 10:13:38 UTC
Fixed, see bug 277492.