Izumi Tsutsui | 4 Mar 2011 14:16
Picon
Gravatar

Re: /build.sh error

> I am guessing the CVS sync didn't occur correctly then?

No idea about cvs environment, but errors were caused by
inconsistent source tree.

---
Izumi Tsutsui

Kieran Jacobsen | 5 Mar 2011 01:05

RE: /build.sh error

Hmm, I might try hitting another mirror and will see what is happening.

-----Original Message-----
From: Izumi Tsutsui [mailto:tsutsui <at> ceres.dti.ne.jp] 
Sent: Friday, 4 March 2011 11:16 PM
To: Kieran Jacobsen
Cc: port-mips <at> NetBSD.org; tsutsui <at> ceres.dti.ne.jp
Subject: Re: /build.sh error

> I am guessing the CVS sync didn't occur correctly then?

No idea about cvs environment, but errors were caused by inconsistent source
tree.

---
Izumi Tsutsui

Attachment (smime.p7s): application/pkcs7-signature, 4915 bytes
Kieran Jacobsen | 5 Mar 2011 09:01

RE: /build.sh error

What are you using to maintain your source tree?

-----Original Message-----
From: Izumi Tsutsui <tsutsui <at> ceres.dti.ne.jp>
Sent: Friday, 4 March 2011 11:16 PM
To: Kieran Jacobsen <kieran <at> kjacobsen.net>
Cc: port-mips <at> NetBSD.org <port-mips <at> NetBSD.org>; tsutsui <at> ceres.dti.ne.jp <tsutsui <at> ceres.dti.ne.jp>
Subject: Re: /build.sh error

> I am guessing the CVS sync didn't occur correctly then?

No idea about cvs environment, but errors were caused by
inconsistent source tree.

---
Izumi Tsutsui

Izumi Tsutsui | 5 Mar 2011 12:12
Picon
Gravatar

Re: /build.sh error

> What are you using to maintain your source tree?

I think anoncvs.NetBSD.org is enough,
but source sets in daily build is easier
to fetch the latest netbsd-5 sources.

http://nyftp.NetBSD.org/pub/NetBSD-daily/netbsd-5/201103040500Z/source/sets/
http://releng.NetBSD.org/

---
Izumi Tsutsui

Kieran Jacobsen | 15 Mar 2011 10:57

RE: /build.sh error

Ok, downloaded the latest set of sources and extracted them to /usr/src. And now things look pretty much the
same after running the build.sh again.

./usr/share/man/man8/dnssec-dsfromkey.8
./usr/share/man/man8/dnssec-keyfromlabel.8
./usr/share/man/man8/dnssec-revoke.8
./usr/share/man/man8/dnssec-settime.8
=========  end of 203 extra files  ===========

*** Failed target:  checkflist
*** Failed command: cd /usr/src/distrib/sets && DESTDIR=/usr/src/../obj/destdir.cobalt
MACHINE=cobalt MACHINE_ARCH=mipsel AWK=/usr/src/../tools/bin/nbawk
CKSUM=/usr/src/../tools/bin/nbcksum DB=/usr/src/../tools/bin/nbdb HOST_SH=/bin/sh
MAKE=/usr/src/../tools/bin/nbmake MKTEMP=/usr/src/../tools/bin/nbmktemp
MTREE=/usr/src/../tools/bin/nbmtree PAX=/usr/src/../tools/bin/nbpax
SED=/usr/src/../tools/bin/nbsed TSORT=/usr/src/../tools/bin/nbtsort\ -q /bin/sh
/usr/src/distrib/sets/checkflist -M /usr/src/../obj/destdir.cobalt/METALOG.sanitised
*** Error code 1

Stop.
nbmake: stopped in /usr/src/distrib/sets

*** Failed target:  distribution
*** Failed command: _makedirtarget() { dir="$1"; shift; target="$1"; shift; case "${dir}" in /*)
this="${dir}/"; real="${dir}" ;; .) this=""; real="/usr/src" ;; *) this="${dir}/";
real="/usr/src/${dir}" ;; esac; show=${this:-.}; echo "${target} ===> ${show%/}${1:+ (with: $ <at> )}";
cd "${real}" && /usr/src/../tools/bin/nbmake _THISDIR_="${this}" "$ <at> " ${target}; };
_makedirtarget distrib/sets checkflist
*** Error code 1

(Continue reading)

Izumi Tsutsui | 15 Mar 2011 15:08
Picon
Gravatar

Re: /build.sh error

> Ok, downloaded the latest set of sources and extracted them to /usr/src.
> And now things look pretty much the same after running the build.sh again.
> 
> ./usr/share/man/man8/dnssec-dsfromkey.8
> ./usr/share/man/man8/dnssec-keyfromlabel.8
> ./usr/share/man/man8/dnssec-revoke.8
> ./usr/share/man/man8/dnssec-settime.8
> =========  end of 203 extra files  ===========

Well, different files so not same, but
does your host have any definitions in /etc/mk.conf or
shell environment values, like "MKfoo=no" or "NOfoo=" etc?
---
Izumi Tsutsui

Kieran Jacobsen | 15 Mar 2011 15:35

RE: /build.sh error

It is interesting that yes there are more files, I suspect it's the same from last + extras. Perhaps I didn't
clean up enough after the failed build based off CVS?

cat /etc/mk.conf

WRKOBJDIR=/usr/work
DISTDIR=/usr/distfiles
PKG_RCD_SCRIPTS=YES

Env print out

TERM=xterm
SHELL=/bin/csh
SSH_CLIENT=172.16.0.100 21909 22
SSH_TTY=/dev/ttyp0
USER=<removed>
ENV=/home/≤removed>/.shrc
PAGER=more
MAIL=/var/mail/≤removed>
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/pkg/sbin:/usr/pkg/bin:/usr/X11R7/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin
EXINIT=set autoindent
PWD=/home/≤removed>
EDITOR=vi
SHLVL=1
HOME=/root
LOGNAME=<removed>
SSH_CONNECTION=<removed>
_=/usr/bin/su
SU_FROM=<removed>
BLOCKSIZE=1k
(Continue reading)

Izumi Tsutsui | 16 Mar 2011 14:40
Picon
Gravatar

Re: /build.sh error

> It is interesting that yes there are more files,
> I suspect it's the same from last + extras.
> Perhaps I didn't clean up enough after the failed build based off CVS?

It's better to remove all files under DESTDIR before build,
and also all files under /usr/src before extracting new sets.
---
Izumi Tsutsui

Andy Ruhl | 26 Mar 2011 14:01
Picon

Re: pkgsrc build error for g95

On Tue, Feb 22, 2011 at 7:54 PM, Andy Ruhl <acruhl <at> gmail.com> wrote:
> On Sun, Feb 20, 2011 at 6:32 PM, Matt Thomas <jabbathespud <at> gmail.com> wrote:
>> mips1 doesn't support the ll/sc instructions.
>>
>> I would switch it to use the libc mutex stubs.
>
> I'm not what you would call a developer...
>
> Can you give me a hint about how to do this?

This still isn't resolved and this information isn't enough for me to
research it on my own. Can you give me something I can use to try to
figure this out?

I've been going through the work directory for g95 trying to figure
out what you're talking about but I can't find anything.

Thanks.

Andy

Izumi Tsutsui | 30 Mar 2011 17:22
Picon
Gravatar

Re: pkgsrc build error for g95

> >> mips1 doesn't support the ll/sc instructions.
> >>
> >> I would switch it to use the libc mutex stubs.
> >
> > I'm not what you would call a developer...
> >
> > Can you give me a hint about how to do this?
> 
> This still isn't resolved and this information isn't enough for me to
> research it on my own. Can you give me something I can use to try to
> figure this out?
> 
> I've been going through the work directory for g95 trying to figure
> out what you're talking about but I can't find anything.

- modern threading applications require locking primitives
  (mutex, rwlock etc)
- most applications implements their own locking primitives
- locking primitive requires CPU specific "atomic" instructions
  especially for SMP
- on MIPS, ll/sc instruction is required for SMP locking primitives
- only MIPS3 CPUs have ll/sc and MIPS1 CPUs don't have it
  because MIPS1 CPUs are not SMP capable
- most applications don't care almost obsolete MIPS1 machines
- NetBSD still supports MIPS1 and -march=mips1 is default on gcc,
  so it complains ll/sc instruction is not supported by MIPS1

workaround:
- use -march=mips3 -mabi=32 in CFLAGS (or CPUFLAGS etc)
  so gcc/gas accepts ll/sc
(Continue reading)


Gmane