Opened 19 years ago
Closed 19 years ago
#5801 closed defect (fixed)
NEW: mairix
Reported by: | vincent-opdarw@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.0 |
Keywords: | Cc: | yeled@… | |
Port: |
Description
Email index and search tool
The Portfile will be attached...
Attachments (1)
Change History (14)
Changed 19 years ago by vincent-opdarw@…
comment:1 Changed 19 years ago by yeled@…
Thanks Vincent.
I get this on build...
makeinfo mairix.texi makeinfo --no-split --number-sections --html mairix.texi > mairix.html tex mairix.texi make: tex: Command not found make: * [mairix.dvi] Error 127
comment:2 Changed 19 years ago by vincent-opdarw@…
I think that any error for "make docs" can be ignored: the effect would just be that some doc formats won't be installed. I don't know what is the best way to do this. Perhaps
destroot {
system "cd ${worksrcpath} && make" system "cd ${worksrcpath} && make install" system "cd ${worksrcpath} && make docs | | true" system "cd ${worksrcpath} && make install_docs"
}
comment:5 Changed 19 years ago by vincent-opdarw@…
Well, for users who have installed tex, mairix.pdf could be useful. I think the solution to ignore errors when generating the docs would be better. Or a pdfdoc variant.
comment:6 Changed 19 years ago by vincent-opdarw@…
Also, why this "depends_build port:bison"? Users shouldn't be forced to install the bison port. Or is there a bug in the Mac OS X one?
Anyway, there doesn't seem to be any reference to bison in the mairix archive.
comment:7 Changed 19 years ago by yeled@…
Resolution: | fixed |
---|---|
Status: | closed → reopened |
(In reply to comment #6)
Well, for users who have installed tex, mairix.pdf could be useful. I think the solution to ignore errors when generating the docs would be better. Or a pdfdoc variant.
you can set a test for tex being installed, and then rewrite the target, but i figured making it install was a priority, as we have other docs. pdf seems extraneous.
comment:8 Changed 19 years ago by yeled@…
Status: | reopened → assigned |
---|
(In reply to comment #7)
Also, why this "depends_build port:bison"? Users shouldn't be forced to install the bison port. Or is there a bug in the Mac OS X one?
Anyway, there doesn't seem to be any reference to bison in the mairix archive.
You're right, i saw the dependency but I keep forgetting we are targetting only OSX these days. (which comes with bison)
I've deleted that line.
comment:9 Changed 19 years ago by pkern@…
Cc: | yeled@… added |
---|
(In reply to comment #9)
You're right, i saw the dependency but I keep forgetting we are targetting only OSX these days. (which comes with bison)
Please remember that the bison port is *sometimes* needed, because it installs 2.1 instead of the 1.28 delivered by OS X. So you should check that it really works with stock bison by deactivating the port.
comment:10 Changed 19 years ago by vincent-opdarw@…
I still don't see where bison is used in order to build mairix.
comment:11 Changed 19 years ago by yeled@…
(In reply to comment #11)
I still don't see where bison is used in order to build mairix.
if [ -d dfasyn ]; then cd dfasyn ; make CC="gcc" CFLAGS="-O2 -Wall -DHAS_STDINT_H - DHAS_INTTYPES_H -DUSE_GZIP_MBOX" ; else echo "No dfasyn subdirectory?" ; exit 1 ; fi bison -v -d parse.y mv parse.tab.c parse.c
comment:12 Changed 19 years ago by vincent-opdarw@…
Oops, yes, it seems that I've forgotten another time the -r switch for grep.
Re comment 10, when I submitted the portfile, I hadn't had the bison port yet, so bison 1.28 was used, and it was working.
Portfile for mairix 0.17