There must be something strange about my machine, as other people apparently can install and run linux-opengroupware, but I can't figure out how they do it. I've run into a number of problems trying to get this port installed an running. 1) In the Makefile, CPIOFLAGS includes --no-absolute-filenames. This option is not supported by cpio on my system: # /usr/bin/cpio --no-absolute-filenames cpio: unrecognized option `--no-absolute-filenames' cpio does support --absolute-filenames, which makes me think the condition you are looking for is the default. I worked around this by removing --no-absolute-filenames from CPIOFLAGS 2) The ogo.sh and zideshow.sh start script try to use su(1) with the -c option to specify a command to run. The -c option does not specify a command. It specifies a login class. Ah, I found it. At one point, -c was not an su(1) option. It would be passed to /bin/sh to interpret. However, the CVS logs show FreeBSD added the -c option to su(1) back in October of 1997. At first it was conditionalized by LOGIN_CAP, but that was removed in 1.34.2.4 back in June 2002. The opengroupware port wasn't created until October 2003, so I'm not sure how it ever worked (I must be missing something in the su(1) CVS logs). I worked around this by removing the -c argument and removing the comments. As in: su -l ${OGO_USER} \ ./WOApps/OpenGroupware.woa/ix86/linux-gnu/gnu-fd-nil/OpenGroupware -WOHttpAllowHost '(localhost, you.yourdomain.org)' >>${LOG} 2>&1 & 3) Then I ran into unresolved libraries. OpenGroupware wants to link against libssl.so.0.9.6, but all I have in /compat/linux/lib is libssl.so.0.9.6b. The port does create a symbolic link for libssl.so.9.6 that points to libssl.so.0.9.6b, so I created a new one for libssl.so.0.9.6. The same thing applies to libcrypt.0.9.6. 4) Now I can start OpenGroupware by hand, but when I try to start it via the ogo.sh script, I get the following error in /var/log/opengroupware/ogo.log: ./WOApps/OpenGroupware.woa/ix86/linux-gnu/gnu-fd-nil/OpenGroupware: ./WOApps/OpenGroupware.woa/ix86/linux-gnu/gnu-fd-nil/OpenGroupware: cannot execute binary file I think the "cannot execute binary file" message comes from bash(1), but I cannot tell if it is the linux bash or the FreeBSD native bash I've installed. I can't figure out why it would be displayed either as OpenGroupware has 755 privileges. Fix: I've listed some partial fixes above, but now I'm stuck with the "cannot execute binary file" error. I'm not sure what to do next. How-To-Repeat: Try to install and run misc/linux-opengroupware from the ports collection.
State Changed From-To: open->feedback Awaiting maintainers feedback
Hello, I've got a new (source based) version ready and in testing (need to investigate some amd64 issues and general installation behaviour) which eases installation/maintenance and such since it doesn't require linux_base anymore nor is it based on RPMS: http://svn.opengroupware.org/viewcvs/trunk/maintenance/freebsd/ and I plan to send-pr this 'new' port within a couple of weeks. I've contacted the initial reporter of this report (ports/96613) and gave/will give him advise on how to 'early adopt' this newer version. And thus - I hereby kindly request that someone with the proper bits marks the port: misc/linux-opengroupware as BROKEN= will be replaced by a fixed version with migration instructions. EXPIRATION_DATE= 2006-06-15 Thankyou very much! Kind regards, Frank Reppin -- http://www.opengroupware.org
Responsible Changed From-To: freebsd-ports-bugs->bsam I'll take it.
State Changed From-To: feedback->closed The port was removed (EXPIRATION_DATE passed). We are waiting for the native opengroupware port. Thanks for the report.