by forcing the CFLAGS to -O -pipe. Somehow, the alpha build always
tries to enforce a particular -mcpu=ev4 flag which of course cannot be
understood by the (AVR) xgcc later on. This looks to me like a bug in
the cross-compilation environment of gcc, but i'm tired of actually
finding the bug.
The compiled result of avr-gcc MD5 compares equal to something build
from an IA32 host platform.
next version. In the meantime, apply with the port.
FYI, the bug is demonstrated by this program:
#include <stdio.h>
#include <stdlib.h>
#include <pth.h>
static int check_something(void *arg)
{
return (0);
}
static void *thread(void *arg)
{
printf("thread sleeping five seconds...\n");
pth_nap(pth_time(5, 0));
printf("thread is done sleeping\n"); /* bug: we never get here */
return (NULL);
}
int main(int ac, char **av)
{
pth_event_t ev;
pth_init();
pth_spawn(NULL, thread, NULL);
ev = pth_event(PTH_EVENT_FUNC, check_something, NULL, pth_time(2, 0));
while (1)
pth_wait(ev);
}
Since gcc (in the assumption of generating a native compiler) doesn't
want to cbe configured for an alpha*-*-freebsd* system, we hack the
configure script to allow this (similarly to netbsd). In the end, all
this will be ignored anyway since it's getting to become a
cross-compiler.
redirect to a new server, but they don't carry the old files anymore.
Unfortunately, in order to build the new stuff, we'd need a newer
avr-gcc first -- and that one's by now only available directly from
gcc's CVS repo, which is a little too `green' to me. Let's wait
another couple of months until they rolled a newer release of gcc and
binutils, and switch then.
By now, store the old distfile elsewhere.
Submitted by: fenner's ports build survey (very valuable service!)
<support@scitools.com> Tech Support from Understand C/C++ manufacturer,
we are allowed to remove the RESTRICTED tag as well as the LEGAL
warning.
Update to version 1.4 Build 104 from March 8, 2001.
- Correct a port versioning typo:
o Instead of using PORTVERSION=14b104 which both reflects the
distfile naming convention and follows the naming convention used
in this port; we will switch to PORTVERSION=1.4.104 which reflects
the Changelog information
o To avoid "who came before" problems since last port was
PORTVERSION=14b103, BUMP PORTEPOCH.
- Fix a PLIST unnecessary warning
- Version Changelog: http://www.scitools.com/ucpp_build_log.html
- textproc added in category (like astyle)
Ccdoc is a tool for extracting comments from C++ source code and presenting it
in HTML format, very similar to Java's JavaDoc tool. The tagging used in ccdoc
is very similar to that of Javadoc, with adaptations for the C++ specifics, of
course. Ccdoc supports extracting comments from both header and implementation
files.
In contrast to most other C++ doc'ing applications, ccdoc analyses the code
before it has been run through the pre-processor, so things such as macros can
actually be included in the documentation.
It's usage is not quite as straight forward as JavaDoc's, but considering the
quality of the output, it is well worth the effort.
WWW: http://www.joelinoff.com/ccdoc/
PR: 22794
Submitted by: lonewolf@flame.org
I was planning to rename pyncurses into more appropriate py-ncurses
before committing it out, but forgot to do so. Therefore delete
pyncurses and readd it back as py-ncurses.
Py-ncurses is a Ncurses binding for Python.
PR: 18633
Submitted by: adsharma@sharams.dhs.org
- fix installation path of this perl module because this command failed:
perl -M'ConfigReader::DirectiveStyle' -e 1
ConfigReader files have to be put under
lib/perl5/site_perl/%%PERL_VER%%/
instead of
lib/perl5/site_perl/
- now my new port FlowScan finds the ConfigReader::DirectiveStyle PM.
"configure:1271: checking for ConfigReader::DirectiveStyle"
has strange problems downloading it from the author's site. I really puzzled
because I can't reproduce those problems even from freefall.
Submitted by: bento (sorta)
Use EXTRACT_SUFX instead of single DISTFILES (by kuriyama).
Submitted by: Dave Chapeskie <dchapes@ddm.crosswinds.net>
PR: ports/25711
Not reach for: maintainer (mail service unavailable)
AutoGen is a tool designed for generating program files that contain
repetitive text with varied substitutions. Its goal is to simplify the
maintenance of programs that contain large amounts of repetitious text.
This is especially valuable if there are several blocks of such text that
must be kept synchronized.
manually add the dependency for autoheader(1), but don't have the ports
infrastructure run `autoconf' (which clobbered the top-level configure
script).