broken ports
Reinhard Weismann
reinhard.weismann at callooh.com
Thu Oct 6 05:43:41 PDT 2005
Thank you very much for the info's
in the meanwhile, the problem got solved, after upgrading
p5-Mail-DomainKeys-0.23 to 0.80 yesterday, p5-Mail-SpamAssassin upgrade
also worked.
> The reason I'm asking is that segmentation faults are often caused by
> failing hardware (faulty memory chip, overheating CPU etc). In your
> case, hardware fault is even more likely since you noticed yourself
> that the port builds successfully on another machine.
i don't think so, this problem appeared on two of my machines, both
installed with 5.4, but not on another machine with 5.3
regards,
reinhard
On Thu, 06 Oct 2005 15:12:40 +0300
Toomas Aas <toomas.aas at raad.tartu.ee> wrote:
> Reinhard Weismann wrote:
>
> > does anybody know where to report broken ports, or, where to get
> > information if/why a port currently is broken.
>
> From your description I am not at all sure that the port is broken
> in this case. But since you asked...
>
> If you are sure that the port really is broken, you should first see
> whether somebody has already noted this, by going to
> http://www.freebsd.org/support/bugreports.html and searching for
> existing reports on a particular port. You can also look at the
> archive of freebsd-ports mailing list by going to
> http://www.freebsd.org/search/search.html#mailinglists
>
> FreeBSD has a large and active user community, so real port breakage
> is usually found very fast and by the time you notice it, it's very
> likely that the problem has already been found and even fixed.
> Cvsupping your ports tree and trying to build the port again is often
> a quick fix to port build problems.
>
> If you dont see any existing reports on your problem AND YOU ARE
> STILL SURE THAT IT IS ACTUALLY A PROBLEM WITH THE PORT then it's time
> to submit a bug report at
> http://www.freebsd.org/support/bugreports.html
>
> > in this case on my 5.4-RELEASE-p6 (i386) installations, the port
> > mail/p5-Mail-SpamAssassin (p5-Mail-SpamAssassin-3.1.0) does not
> > compile, i.e. i get
> > [..]
> > Segmentation fault (core dumped)
> > *** Error code 139
> > [..]
>
> Does this happen only to this port? Can you build other ports
> successfully? Can you successfully run 'make buildworld'?
>
> The reason I'm asking is that segmentation faults are often caused by
> failing hardware (faulty memory chip, overheating CPU etc). In your
> case, hardware fault is even more likely since you noticed yourself
> that the port builds successfully on another machine.
>
> --
> Toomas Aas
--
If you give Congress a chance to vote on both sides of an issue, it
will always do it.
-- Les Aspin, D., Wisconsin
More information about the freebsd-questions
mailing list