Re: Trying to compiles today Current
On Sun, 29 Mar 2020 15:36:22 +0200
Willem Jan Withagen wrote:
> I keep getting errors in building my ports from portsbuilder.
> But it is with Current/Clang10.
>
> So I'm trying to get a server at that level, but building world
> keeps giving me:
> --- all_subdir_cddl ---
> ld:
> error: /usr/obj/usr/srcs/head/amd64.amd64/tmp/usr/lib/libuutil.so:
> undefined reference to __assfail cc: error: linker command failed
> with exit code 1 (use -v to see invocation) *** [zfs.full] Error code
> 1
>
>
> Completely cleared src and obj, but the error persists.
>
> Current on this system is:
> FreeBSD 13.0-CURRENT #0 r358358: Thu Feb 27 04:40:39 UTC 2020
> r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
>
> How to fix this?
In my case a leftover CFLAGS=-O0 in /etc/make.conf was the culprit
('=' instead of '+=' not being a typo). As another side effect, build
world took about four times as long as usual, before it errored out.
While at it, I of also ran into what's described
in
https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072531.html,
before removing DEBUG_FLAGS from /etc/make.conf.
Conditionalizing the flags to only be pulled in for the directories I
actually wanted them to be relevant for would certainly have helped.
MfG CoCo
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: UFS journal error on 10.0-CURRENT
On Thu, 30 Aug 2012, Jakub Lach wrote: If I were you, I would try regular fsck, as here (9-STABLE) using journal has left me with fs inconsistencies. Could you elaborate on the inconsistencies you encountered ? MfG CoCo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[cft] Small patch for calendar(1)
Hi,
for a while now, calendar(1) seems to have forgotten how to handle what
the man page describes as: 'A month without a day matches the first of
that month.'
A notable result of this is, that the output of 'calendar -f
/usr/share/calendar/calendar.all' is always headed by 'Unprocessed'
error messages.
The attached patch tries to help calendar(1) remember how to do this as
is described in the man page.
Since I'm not an avid calendar(1) user, I'd very much like others to
review and try out the patch, before I go pester commiters by opening a PR.
MfG CoCo
--- src/usr.bin/calendar/parsedata.c.orig 2011-12-31 11:36:40.0
+0100
+++ src/usr.bin/calendar/parsedata.c2011-12-31 11:57:55.0 +0100
@@ -174,11 +174,22 @@
}
if (isonlydigits(date, 1)) {
/* Assume month number only */
- *flags |= F_MONTH;
+ *flags |= (F_MONTH | F_DAYOFMONTH);
+ *idayofmonth = 1;
*imonth = (int)strtol(date, (char **)NULL, 10);
strcpy(month, getmonthname(*imonth));
return(1);
}
+ if ((checkmonth(date, len, offset, pmonth) != 0)) {
+ /* Assume month name only */
+ *flags |= (F_MONTH | F_DAYOFMONTH);
+ *idayofmonth = 1;
+ *imonth = offset;
+ strcpy(month, getmonthname(*imonth));
+ return(1);
+ }
+
+
return (0);
}
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: make installworld fails on releng9
On Thu, 27 Oct 2011, Chuck Burns wrote: I had some issues while running make installworld after I sync'd to the latest releng9, on my RC1 install. Now, it appears to failed, while trying to create some links, chfn chsh ypchpass ypchfn ypchsh. These are supposed to be hardlinked to /usr/bin/chpass, except that, since the other files already exist, and are immutable, make installworld was unable to do anything, so I wound up removing the immutable flag on these files and re- running make installworld. I didn't see any mention of this little.. issue, in UPDATING, or in the - current mailing list (yes, I know, 9.0 is no longer technically, current, but since it isn't released yet, I figure it's close enough) I'm seeing this on head (226827, amd64), also. MfG CoCo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
AMD X2/Opteron Rev E workaround ?
Hi, it's been a while since this topic was touched, see http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013129.html. I coulnd't find anything more recent than the following commit, which prints a warning message, if a suspectible CPU model is detected: http://svn.freebsd.org/viewvc/base?view=revisionrevision=198868 If someone has any patches, even very preliminary ones, I'd be more than happy to give them a thorough try on otherwise unused machines. MfG CoCo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
