Discussion:
[developer] DEBUG build provides non-debug libs?
Richard PALO via illumos-developer
2014-10-17 20:56:59 UTC
Permalink
This may seem like a strange question, but is there something special
needed to get debug turned on other than -F and -D in the options?

My diff of illumos.sh is (as it alwas was) as follows (only the lint
47c47
< export NIGHTLY_OPTIONS='-FnCDAmprt'
---
export NIGHTLY_OPTIONS='-FnCDAlmprt'
60c60
< export GATE='illumos-gate'
---
export GATE='testws'
162,164d161
< if [[ -d "$CODEMGR_WS/.git" ]]; then
< export VERSION="$GATE-$(git log -1 --format=%h)"
< else
166d162
< fi
235d230
< # export ENABLE_SMB_PRINTING='#'
237,243d231
<
< export GCC_ROOT=/opt/gcc-4.4.4
< export CW_NO_SHADOW=1
< export ONNV_BUILDNUM=151012
< export RELEASE_DATE=`git log --pretty=format:%cd --date=short -n 1 | tr - .`
< export i386_LINT=/opt/SUNWspro/bin/lint
< export amd64_LINT=/opt/SUNWspro/bin/lint
nightly.sh is +/- identical with usr/src/tools/scripts/nightly.sh
==== Nightly distributed build started: Sat Oct 11 18:40:27 CEST 2014 ====
==== Nightly distributed build completed: Sat Oct 11 19:31:46 CEST 2014 ====
==== Total build time ====
real 0:51:19
==== Build environment ====
/usr/bin/uname
SunOS omnis 5.11 illumos-gate-d2c7ed4 i86pc i386 i86pc
/opt/SUNWspro/bin/dmake
dmake: Sun Distributed Make 7.9 SunOS_i386 2009/06/03
number of concurrent jobs = 14
32-bit compiler
/opt/onbld/bin/i386/cw -_gcc
cw version 1.29 (SHADOW MODE DISABLED)
primary: /opt/gcc-4.4.4/bin/gcc
gcc (GCC) 4.4.4
64-bit compiler
/opt/onbld/bin/i386/cw -_gcc
cw version 1.29 (SHADOW MODE DISABLED)
primary: /opt/gcc-4.4.4/bin/gcc
gcc (GCC) 4.4.4
/usr/java/bin/javac
openjdk full version "1.7.0_21-b30"
/usr/bin/as
as: Sun Compiler Common 12 SunOS_i386 snv_121 08/03/2009
/usr/ccs/bin/ld
ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1749 (illumos)
Build project: group.staff
Build taskid: 156
==== Nightly argument issues ====
==== Build version ====
illumos-gate-8df0326
==== Make clobber ERRORS ====
==== Make tools clobber ERRORS ====
==== Tools build errors ====
==== Build errors (DEBUG) ====
==== Build warnings (DEBUG) ====
==== Elapsed build time (DEBUG) ====
real 35:38.3
user 3:10:00.7
sys 56:15.1
==== Build noise differences (DEBUG) ====
==== package build errors (DEBUG) ====
==== Validating manifests against proto area ====
==== Check versioning and ABI information ====
==== Check ELF runtime attributes ====
==== Diff ELF runtime attributes (since last build) ====
==== cstyle/hdrchk errors ====
==== Find core files ====
==== Check lists of files ====
==== Impact on file permissions ====
libadm.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libaio.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libavl.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libbsm.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libc_db.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libc.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libcmdutils.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libcontract.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libcryptoutil.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libctf.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libcurses.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdevice.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdevid.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdevinfo.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdhcpagent.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdhcputil.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdl.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdladm.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdlpi.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libdoor.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libefi.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libelf.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libelfsign.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libfdisk.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libgen.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libgrubmgmt.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libinetutil.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libintl.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libipadm.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libipmp.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libkcfd.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libkmf.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libkmfberder.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libkstat.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libmd.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libmd5.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libmeta.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libmp.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libMPAPI.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libmpscsi_vhci.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libnsl.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libnvpair.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libnwam.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libpam.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libposix4.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libproc.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libpthread.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
librcm.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libresolv.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
librestart.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
librpcsvc.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
librt.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
librtld_db.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libscf.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libsec.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libsecdb.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libsendfile.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libsocket.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libsysevent.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libtermcap.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libtermlib.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libthread_db.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libthread.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libtsnet.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libtsol.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libumem.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libuuid.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libuutil.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libw.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libxnet.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libzfs_core.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
libzfs.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, not stripped, no debugging information available
I found this trying to debug libc printing function where, with verbose
(gdb) start
Temporary breakpoint 1 at 0x8050d16: file cflt3.c, line 8.
Starting program: /home/richard/src/tfor/cflt3
Reading symbols from /usr/lib/ld.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/ld.so.1
Reading symbols from /home/richard/src/illumos-gate/proto/root_i386/lib/libc.so.1...(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
Loaded symbols for /home/richard/src/illumos-gate/proto/root_i386/lib/libc.so.1
[New Thread 1 (LWP 1)]
A helping hand please?


-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Richard Lowe via illumos-developer
2014-10-17 21:37:51 UTC
Permalink
DEBUG implies assertions and such are enabled, if you want DWARF to
remain you need to use SOURCEDEBUG=yes


-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Richard PALO via illumos-developer
2014-10-20 08:05:22 UTC
Permalink
Post by Richard Lowe via illumos-developer
DEBUG implies assertions and such are enabled, if you want DWARF to
remain you need to use SOURCEDEBUG=yes
Thanks, by the way, are the messages of the following sort okay and to
Post by Richard Lowe via illumos-developer
==== Nightly distributed build started: Mon Oct 20 07:26:19 CEST 2014 ====
==== Nightly distributed build completed: Mon Oct 20 08:00:16 CEST 2014 ====
==== Total build time ====
real 0:33:57
==== Build environment ====
/usr/bin/uname
SunOS omnis 5.11 omnios-f800a71 i86pc i386 i86pc
/opt/SUNWspro/bin/dmake
dmake: Sun Distributed Make 7.9 SunOS_i386 2009/06/03
number of concurrent jobs = 14
32-bit compiler
/opt/onbld/bin/i386/cw -_gcc
cw version 1.29 (SHADOW MODE DISABLED)
primary: /opt/gcc-4.4.4/bin/gcc
gcc (GCC) 4.4.4
64-bit compiler
/opt/onbld/bin/i386/cw -_gcc
cw version 1.29 (SHADOW MODE DISABLED)
primary: /opt/gcc-4.4.4/bin/gcc
gcc (GCC) 4.4.4
/usr/java/bin/javac
openjdk full version "1.7.0_21-b30"
/usr/bin/as
as: Sun Compiler Common 12 SunOS_i386 snv_121 08/03/2009
/usr/ccs/bin/ld
ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1749 (illumos)
Build project: group.staff
Build taskid: 84
==== Nightly argument issues ====
==== Build version ====
illumos-gate-84a98f5
==== Make clobber ERRORS ====
==== Make tools clobber ERRORS ====
==== Tools build errors ====
==== Build errors (DEBUG) ====
==== Build warnings (DEBUG) ====
ld: warning: relocation error: R_AMD64_64: file obj64/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file obj64/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file debug64/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file debug64/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file obj32/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file obj32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol t0: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file pics/__fex_i386.o: symbol _sse_hw: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
==== Elapsed build time (DEBUG) ====
real 29:46.8
user 3:19:40.3
sys 23:26.2
==== Build noise differences (DEBUG) ====
202a203
ld: warning: relocation error: R_386_32: file pics/__fex_i386.o: symbol _sse_hw: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
==== cstyle/hdrchk errors ====
==== Find core files ====
==== Check lists of files ====
-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Dan McDonald via illumos-developer
2014-10-20 12:54:38 UTC
Permalink
==== Build warnings (DEBUG) ====
ld: warning: relocation error: R_AMD64_64: file obj64/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file obj64/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file debug64/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file debug64/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file obj32/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file obj32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol t0: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file pics/__fex_i386.o: symbol _sse_hw: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
No they're not, but I do not see these on my build boxes at all. Do you do "make clobber" or do you do incremental builds? Also, these are in the kernel, which wasn't affected at all by the libm integration.

Dan




-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Richard PALO via illumos-developer
2014-10-20 13:06:14 UTC
Permalink
Post by Dan McDonald via illumos-developer
==== Build warnings (DEBUG) ====
ld: warning: relocation error: R_AMD64_64: file obj64/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file obj64/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file debug64/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_AMD64_64: file debug64/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file obj32/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file obj32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pageoffset: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol _pagesize: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file debug32/genunix: symbol t0: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
ld: warning: relocation error: R_386_32: file pics/__fex_i386.o: symbol _sse_hw: external symbolic relocation against non-allocatable section .debug_info; cannot be processed at runtime: relocation ignored
No they're not, but I do not see these on my build boxes at all. Do you do "make clobber" or do you do incremental builds? Also, these are in the kernel, which wasn't affected at all by the libm integration.
Dan
This is a full nightly invoked as '$ ./nightly.sh illumos.sh'
(and normally I prefix with a ptime, but that new issue I posted in the
omnios discussion list).

That is, yes, clobber is the first step of a full nightly.

NB, if you build via omnios-build/build/illumos, that's not the way I do
it... I am building a branch based upon 'illumos-omnios' though.

I should mention that this was the first build after upgrading from
omnios 151012 to b151013, but normally speaking, that shouldn't make a
bit of a difference given a clobber...

I certainly don't need to blow my packages and proto directories, do I?




-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Dan McDonald via illumos-developer
2014-10-20 14:46:44 UTC
Permalink
Post by Richard PALO via illumos-developer
This is a full nightly invoked as '$ ./nightly.sh illumos.sh'
(and normally I prefix with a ptime, but that new issue I posted in the omnios discussion list).
Like I said, I'd like to see that reproduced with a script smaller than "nightly.sh" if possible.
Post by Richard PALO via illumos-developer
That is, yes, clobber is the first step of a full nightly.
Hmm. Not sure why you'd see the genunix problems you're reporting.
Post by Richard PALO via illumos-developer
NB, if you build via omnios-build/build/illumos, that's not the way I do it... I am building a branch based upon 'illumos-omnios' though.
Which branch? And what changes have you made?
Post by Richard PALO via illumos-developer
I should mention that this was the first build after upgrading from omnios 151012 to b151013, but normally speaking, that shouldn't make a bit of a difference given a clobber...
I certainly don't need to blow my packages and proto directories, do I?
You shouldn't, but now I'm curious what changes you made? My builds are the ones that go out on github (or works in progress that END UP going out on github).

Dan



-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Richard PALO via illumos-developer
2014-10-20 16:28:34 UTC
Permalink
Post by Dan McDonald via illumos-developer
Post by Richard PALO via illumos-developer
This is a full nightly invoked as '$ ./nightly.sh illumos.sh'
(and normally I prefix with a ptime, but that new issue I posted in the omnios discussion list).
Like I said, I'd like to see that reproduced with a script smaller than "nightly.sh" if possible.
I'll see if I come across with something, may not be soon.
Post by Dan McDonald via illumos-developer
Post by Richard PALO via illumos-developer
That is, yes, clobber is the first step of a full nightly.
Hmm. Not sure why you'd see the genunix problems you're reporting.
Post by Richard PALO via illumos-developer
NB, if you build via omnios-build/build/illumos, that's not the way I do it... I am building a branch based upon 'illumos-omnios' though.
Which branch? And what changes have you made?
My dev branch is rebased off of illumos-omnios. This contains
basically the acpica v5.1 update as well as illumos #5218 and #2732.

The issue now is since adding 'SOURCEDEBUG=yes', but perhaps upgrading
from r151012 to b151013 has something else to do with it as well...

I haven't yet onu'd to my bits based upon b151013 yet, but I've been
running them upon 'stable' since reverting after your message about the
toxique bloody awhile back... now I wanted native libm!

I could just as easy rebuild pure illumos-omnios, no problem to try.
Post by Dan McDonald via illumos-developer
Post by Richard PALO via illumos-developer
I should mention that this was the first build after upgrading from omnios 151012 to b151013, but normally speaking, that shouldn't make a bit of a difference given a clobber...
I certainly don't need to blow my packages and proto directories, do I?
You shouldn't, but now I'm curious what changes you made? My builds are the ones that go out on github (or works in progress that END UP going out on github).
Dan
Yes, I track the omnios github master as illumos-omnios, already having
illumos upstream in my repository.

[remote "illumos-omnios"]
url = git://github.com/omniti-labs/illumos-omnios.git
fetch = +refs/heads/*:refs/remotes/illumos-omnios/*
[branch "illumos-omnios"]
remote = illumos-omnios
merge = refs/heads/master

BTW it is a nightmare merging upstream separately from illumos-omnios, I
always seem to need to git reset hard my illumos-omnios branch to
illumos-omnios/master to get things back in order. So I basically don't
do that anymore... glad you merge frequently now.



-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Richard Lowe via illumos-developer
2014-10-20 16:13:48 UTC
Permalink
Dan, you missed the bit where I pointed him to the SOURCEDEBUG stuff
and he (I assume) enabled it for the whole build. :)


-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Gordon Ross via illumos-developer
2014-10-20 16:24:16 UTC
Permalink
Yeah, I don't think SOURCEDEBUG woks everywhere.
With the "fksmbd" work, we found libraries that don't link if you
compile with -g (and I never figured out why).


On Mon, Oct 20, 2014 at 12:13 PM, Richard Lowe via illumos-developer
Post by Richard Lowe via illumos-developer
Dan, you missed the bit where I pointed him to the SOURCEDEBUG stuff
and he (I assume) enabled it for the whole build. :)
-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175074-7782178a
Modify Your Subscription: https://www.listbox.com/member/?&
Powered by Listbox: http://www.listbox.com
-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Richard Lowe via illumos-developer
2014-10-20 16:32:04 UTC
Permalink
Gordon, when we talked about this before, the libraries you named
worked just fine for me.
If you're still having problems, can you reproduce them and tell me
how, and I can go and fix them for you.

(also, nothing in Richard's mail message is an outright failure to
link, so it seems like it worked better for him than you, too).


-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com

Richard Lowe via illumos-developer
2014-10-20 16:13:10 UTC
Permalink
I don't think they're particularly _expected_, but I'd intended
SOURCEDEBUG to be used when building specific components, not the
entire system.

I understand why the messages are happening, but I hadn't really
expected them. I doubt they're harmful (unless, somehow, you have the
means to make use of that DWARF, which it may mess up).


-------------------------------------------
illumos-developer
Archives: https://www.listbox.com/member/archive/182179/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182179/21175072-86d49504
Modify Your Subscription: https://www.listbox.com/member/?member_id=21175072&id_secret=21175072-abdf7b7e
Powered by Listbox: http://www.listbox.com
Loading...