2013-12-06 12:04:52 +01:00
|
|
|
# $NetBSD: shl.mi,v 1.258 2013/11/16 13:01:38 alnsn Exp $
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
#
|
|
|
|
|
# Note: don't delete entries from here - mark them as "obsolete" instead.
|
|
|
|
|
#
|
|
|
|
|
./usr/lib/crtbeginS.o comp-c-lib
|
|
|
|
|
./usr/lib/crtbeginT.o comp-c-lib
|
|
|
|
|
./usr/lib/crtendS.o comp-c-lib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libamu_pic.a comp-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libarchive_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libasn1_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libatf-c++_pic.a comp-atf-piclib atf
|
|
|
|
|
./usr/lib/libatf-c_pic.a comp-atf-piclib atf
|
|
|
|
|
./usr/lib/libatf_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libavl_pic.a comp-zfs-piclib zfs
|
|
|
|
|
./usr/lib/libbind9_pic.a comp-bind-piclib
|
|
|
|
|
./usr/lib/libbluetooth_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libbsdmalloc_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libbz2_pic.a comp-c-piclib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libc++_pic.a comp-c-piclib libcxx
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libc_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libcdk_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libcom_err_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libcompat_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libcrypt_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libcrypto_pic.a comp-c-piclib crypto
|
|
|
|
|
./usr/lib/libctf_pic.a comp-c-piclib dtrace
|
|
|
|
|
./usr/lib/libcurses_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libdes_pic.a comp-c-piclib crypto
|
|
|
|
|
./usr/lib/libdevmapper_pic.a comp-lvm-piclib lvm
|
|
|
|
|
./usr/lib/libdm_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libdns_pic.a comp-bind-piclib
|
|
|
|
|
./usr/lib/libdns_sd_pic.a comp-mdns-piclib mdns
|
|
|
|
|
./usr/lib/libdtrace_pic.a comp-c-piclib dtrace
|
|
|
|
|
./usr/lib/libdwarf_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libedit_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libelf_pic.a comp-c-piclib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libevent_openssl_pic.a comp-c-piclib crypto
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libevent_pic.a comp-c-piclib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libevent_pthreads_pic.a comp-c-piclib
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libexecinfo_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libexpat_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libfetch_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libform_pic.a comp-c-piclib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libg++_pic.a comp-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libg2c_pic.a comp-fortran-lib gcc=3
|
|
|
|
|
./usr/lib/libg2c_pic.a comp-obsolete gcc=4,obsolete
|
|
|
|
|
./usr/lib/libgcc_eh.a comp-c-lib gcccmds
|
|
|
|
|
./usr/lib/libgcc_eh_p.a comp-c-proflib obsolete
|
|
|
|
|
./usr/lib/libgcc_eh_pic.a comp-c-piclib obsolete
|
|
|
|
|
./usr/lib/libgcc_pic.a comp-c-lib gcc=4
|
|
|
|
|
./usr/lib/libgcc_pic.a comp-c-lib obsolete,gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libgcc_pic.a comp-c-lib obsolete,gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libgmp.so comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libgmp.so.10 comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libgmp.so.10.2 comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libgmp_pic.a comp-c-piclib obsolete
|
|
|
|
|
./usr/lib/libgnumalloc_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libgomp_pic.a comp-c-piclib gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libgomp_pic.a comp-c-piclib gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libgssapi_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libhdb_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libheimbase_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libheimntlm_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libhx509_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libintl_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libipsec_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libisc_pic.a comp-bind-piclib
|
|
|
|
|
./usr/lib/libisccc_pic.a comp-bind-piclib
|
|
|
|
|
./usr/lib/libisccfg_pic.a comp-bind-piclib
|
|
|
|
|
./usr/lib/libiscsi_pic.a comp-c-piclib iscsi
|
|
|
|
|
./usr/lib/libisns_pic.a comp-isns-piclib
|
|
|
|
|
./usr/lib/libkadm5clnt_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libkadm5srv_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libkadm_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libkafs_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libkdb_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libkdc_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libkrb5_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libkrb_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libkstream_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libkvm_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/liblber_pic.a comp-ldap-piclib ldap
|
|
|
|
|
./usr/lib/libldap_pic.a comp-ldap-piclib ldap
|
|
|
|
|
./usr/lib/libldap_r_pic.a comp-ldap-piclib ldap
|
|
|
|
|
./usr/lib/liblua_pic.a comp-c-piclib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/liblutok_pic.a comp-c-piclib kyua
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/liblwres_pic.a comp-bind-piclib
|
|
|
|
|
./usr/lib/liblzf_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/liblzma_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libm_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libmagic_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libmenu_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libmj_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libmpc.so comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libmpc.so.2 comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libmpc.so.2.0 comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libmpc_pic.a comp-c-piclib obsolete
|
|
|
|
|
./usr/lib/libmpfr.so comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libmpfr.so.4 comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libmpfr.so.4.1 comp-c-shlib obsolete
|
|
|
|
|
./usr/lib/libmpfr_pic.a comp-c-piclib obsolete
|
|
|
|
|
./usr/lib/libmudflap.so comp-c-shlib gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libmudflap.so comp-c-shlib gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libmudflap.so.0 comp-c-shlib gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libmudflap.so.0 comp-c-shlib gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libmudflap.so.0.0 comp-c-shlib gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libmudflap.so.0.0 comp-c-shlib gcc=48
|
|
|
|
|
./usr/lib/libmudflap_pic.a comp-c-piclib gcc=45
|
|
|
|
|
./usr/lib/libmudflap_pic.a comp-c-piclib gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libmudflapth.so comp-c-shlib gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libmudflapth.so comp-c-shlib gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libmudflapth.so.0 comp-c-shlib gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libmudflapth.so.0 comp-c-shlib gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libmudflapth.so.0.0 comp-c-shlib gcc=45
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libmudflapth.so.0.0 comp-c-shlib gcc=48
|
|
|
|
|
./usr/lib/libmudflapth_pic.a comp-c-piclib gcc=45
|
|
|
|
|
./usr/lib/libmudflapth_pic.a comp-c-piclib gcc=48
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libnetpgp_pic.a comp-c-piclib crypto
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libnetpgpverify_pic.a comp-c-piclib crypto
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libnpf_pic.a comp-npf-piclib npf
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libntp_pic.a comp-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libnvpair_pic.a comp-zfs-piclib zfs
|
|
|
|
|
./usr/lib/libobjc_pic.a comp-objc-piclib gcccmds
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libopcodes.so.6 comp-c-shlib binutils
|
|
|
|
|
./usr/lib/libopcodes.so.6.0 comp-c-shlib binutils
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libopenpgpsdk_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libossaudio_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libp2k_pic.a comp-puffs-piclib rump
|
|
|
|
|
./usr/lib/libpam_pic.a comp-c-piclib pam
|
|
|
|
|
./usr/lib/libpcap_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libpcc_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libpci_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libperfuse_pic.a comp-perfuse-piclib
|
|
|
|
|
./usr/lib/libposix_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libppath_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libprop_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libpthread_dbg_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libpthread_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libpuffs_pic.a comp-puffs-piclib
|
|
|
|
|
./usr/lib/libquota_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libradius_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/librefuse_pic.a comp-refuse-piclib
|
|
|
|
|
./usr/lib/libresolv_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libroken_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/librpcsvc_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/librt_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/librump_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpclient_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpcrypto_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/librumpdev_audio_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_bpf_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_cgd_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_disk_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_dm_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_drvctl_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_fss_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_md_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_netsmb_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_pad_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_pud_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_putter_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_raidframe_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_rnd_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_scsipi_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_scsitest_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_sysmon_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_ubt_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_ucom_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_ugenhc_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_ulpt_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_umass_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_usb_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpdev_wscons_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_cd9660_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_efs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_ext2fs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_fdesc_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_ffs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_hfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_kernfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_lfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_mfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_msdos_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_nfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_nfsserver_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_nilfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_ntfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_null_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_nullfs_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/librumpfs_ptyfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_smbfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_syspuffs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_sysvbfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_tmpfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_udf_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_ufs_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/librumpfs_umap_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_umapfs_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/librumpfs_union_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_v7fs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpfs_zfs_pic.a comp-c-piclib zfs,rump
|
|
|
|
|
./usr/lib/librumphijack_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpkern_crypto_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpkern_ksem_pic.a comp-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/librumpkern_sljit_pic.a comp-c-piclib sljit,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/librumpkern_solaris_pic.a comp-c-piclib zfs,rump
|
|
|
|
|
./usr/lib/librumpkern_tty_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpkern_z_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_agr_pic.a comp-c-piclib rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/librumpnet_bpfjit_pic.a comp-c-piclib sljit,rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/librumpnet_bridge_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_local_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_net80211_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_net_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_netbt_pic.a comp-c-piclib rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/librumpnet_netinet6_pic.a comp-c-piclib rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/librumpnet_netinet_pic.a comp-c-piclib rump
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/librumpnet_netmpls_pic.a comp-c-piclib rump
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/librumpnet_npf_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_shmif_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_sockin_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpnet_virtif_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpuser_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpvfs_fifofs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpvfs_layerfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/librumpvfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/libsaslc_pic.a comp-c-piclib crypto
|
|
|
|
|
./usr/lib/libsdp_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libskey_pic.a comp-c-piclib skey
|
|
|
|
|
./usr/lib/libsl_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libsqlite3_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libss_pic.a comp-obsolete obsolete
|
|
|
|
|
./usr/lib/libssh_pic.a comp-c-piclib crypto
|
|
|
|
|
./usr/lib/libssl_pic.a comp-c-piclib crypto
|
|
|
|
|
./usr/lib/libssp_pic.a comp-obsolete obsolete
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libstdc++_pic.a comp-cxx-piclib cxx,gcccmds,libstdcxx
|
|
|
|
|
./usr/lib/libtddl_pic.a comp-c-piclib tpm
|
|
|
|
|
./usr/lib/libtelnet_pic.a comp-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libtermcap_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libterminfo_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libtermlib_pic.a comp-c-piclib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libtpm_unseal_pic.a comp-tpm-lib tpm
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libtre_pic.a comp-c-piclib
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libtspi_pic.a comp-c-piclib tpm
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libukfs_pic.a comp-c-piclib rump
|
|
|
|
|
./usr/lib/libumem_pic.a comp-zfs-piclib zfs
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/lib/libusb_pic.a comp-obsolete obsolete
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
./usr/lib/libusbhid_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libutil_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libuutil_pic.a comp-zfs-piclib zfs
|
|
|
|
|
./usr/lib/libwind_pic.a comp-c-piclib kerberos
|
|
|
|
|
./usr/lib/libwrap_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libz_pic.a comp-c-piclib
|
|
|
|
|
./usr/lib/libzfs_pic.a comp-zfs-piclib zfs
|
2013-12-06 12:04:52 +01:00
|
|
|
./usr/libexec/liblto_plugin.so comp-c-bin gcc=48
|
|
|
|
|
./usr/libexec/liblto_plugin.so.0 comp-c-bin gcc=48
|
|
|
|
|
./usr/libexec/liblto_plugin.so.0.0 comp-c-bin gcc=48
|