Bug 239388 - devel/apr1: Fails to build - "configure: error: cannot compute sizeof (char)"
Summary: devel/apr1: Fails to build - "configure: error: cannot compute sizeof (char)"
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-apache (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-22 21:51 UTC by Mike
Modified: 2019-07-23 19:08 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2019-07-22 21:51:06 UTC
# make

....

checking for h_errno in netdb.h... yes
checking for off_t... (cached) yes
checking for pid_t... (cached) yes
checking for size_t... (cached) yes
checking for uid_t in sys/types.h... (cached) yes
checking for ssize_t... (cached) yes
checking for inline... inline
checking for an ANSI C-conforming const... yes
checking whether setpgrp takes no argument... yes
checking for socklen_t... yes
checking size of void*... 0
checking size of char... configure: error: in `/var/ports/usr/ports/devel/apr1/work/apr-1.6.5':
configure: error: cannot compute sizeof (char)
See `config.log' for more details
*** Error code 77

Stop.
make[1]: stopped in /usr/ports/devel/apr1
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/apr1
Comment 2 Mike 2019-07-23 18:57:39 UTC
Installed ports in new jail from scratch:

....

portsnap fetch
portsnap extract
cd /usr/ports/devel/apr1
make

--- config-conditional ---
--- do-config ---
===> Building/installing dialog4ports as it is required for the config dialog
--- limited-clean-depends-noflavor ---
--- config-conditional ---
--- limited-clean-depends-noflavor ---
--- limited-clean-depends ---
--- config-conditional ---
--- config ---
===> Skipping 'config' as NO_DIALOG is defined
--- install ---
--- /usr/ports/ports-mgmt/dialog4ports/work/.stage_done.dialog4ports._usr_local ---
--- fake-pkg ---
--- security-check ---
--- install-message ---
===>   Registering installation for dialog4ports-0.1.6
===>  Installing for dialog4ports-0.1.6
--- check-already-installed ---
--- fake-pkg ---
pkg-static: open(/usr/ports/ports-mgmt/dialog4ports/work/.metadir): No such file or directory
--- check-already-installed ---
===>  Checking if dialog4ports is already installed
--- fake-pkg ---
*** [fake-pkg] Error code 70

make[3]: stopped in /usr/ports/ports-mgmt/dialog4ports
1 error

make[3]: stopped in /usr/ports/ports-mgmt/dialog4ports
*** [install] Error code 2

make[2]: stopped in /usr/ports/ports-mgmt/dialog4ports
--- limited-clean-depends-noflavor ---
A failure has been detected in another branch of the parallel make

make[3]: stopped in /usr/ports/ports-mgmt/dialog4ports
*** [limited-clean-depends-noflavor] Error code 2

make[2]: stopped in /usr/ports/ports-mgmt/dialog4ports
2 errors

make[2]: stopped in /usr/ports/ports-mgmt/dialog4ports
===> Options unchanged
A failure has been detected in another branch of the parallel make

make[1]: stopped in /usr/ports/devel/apr1
*** [config-conditional] Error code 2

make: stopped in /usr/ports/devel/apr1
1 error

make: stopped in /usr/ports/devel/apr1

....


Nowhere do I have NO_DIALOG. /etc/make.conf is empty. I have no idea why that won't come up, or why dialog4ports wont build. So I just install it from scratch and try to proceed:

....

apr1 # pkg install dialog4ports
Proceed with this action? [y/N]: y
[1/1] Installing dialog4ports-0.1.6...
[1/1] Extracting dialog4ports-0.1.6: 100%

apr1 # make

--- config-conditional ---
--- do-config ---
*** [do-config] Stopped -- signal 22


...


And it just hangs. This happens in the blank jail. So I do same steps in main host just in case its some weird jail issue. Same result.

I've never had these kinds of problems from ports. Nothing builds. 

....
cd shells/bash
n1 bash # make
--- config-conditional ---
--- do-config ---
*** [do-config] Stopped -- signal 22
....


This vanilla FreeBSD 12.
Comment 3 Mike 2019-07-23 19:07:06 UTC
I have no idea what is in my environment that made it mad. But running from stock shell (not bash) worked fine. So its something in my shell environment that was causing problems.