Re: kbuild

2018-04-18 Thread Walter Schwarzenfeld

Solved, seems it was my error (maybe, it was an entry in etc/make.conf).

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


kbuild

2018-04-17 Thread Walter Schwarzenfeld

fails to build

n file included from 
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/commands.c:19:0:
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/commands.c: In 
function 'delete_target':
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/make.h:872:52: 
error: 'errno' undeclared (first use in this function)

 #define EINTRLOOP(_v,_c)   while (((_v)=_c)==-1 && errno==EINTR)
    ^
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/commands.c:856:3: 
note: in expansion of macro 'EINTRLOOP'

   EINTRLOOP (e, stat (file->name, ));
   ^
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/make.h:872:52: 
note: each undeclared identifier is reported only once for each function 
it appears in

 #define EINTRLOOP(_v,_c)   while (((_v)=_c)==-1 && errno==EINTR)
    ^
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/commands.c:856:3: 
note: in expansion of macro 'EINTRLOOP'

   EINTRLOOP (e, stat (file->name, ));
   ^
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/make.h:872:59: 
error: 'EINTR' undeclared (first use in this function)

 #define EINTRLOOP(_v,_c)   while (((_v)=_c)==-1 && errno==EINTR)
   ^
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/commands.c:856:3: 
note: in expansion of macro 'EINTRLOOP'

   EINTRLOOP (e, stat (file->name, ));
   ^~~~~
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/commands.c:865:11: 
warning: implicit declaration of function 'unlink' 
[-Wimplicit-function-declaration]

   if (unlink (file->name) < 0
   ^~
/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/commands.c:866:16: 
error: 'ENOENT' undeclared (first use in this function)

    && errno != ENOENT) /* It disappeared; so what.  */
    ^~
gmake[5]: *** [Makefile:845: commands.o] Error 1
gmake[5]: Leaving directory 
'/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/kmk'

gmake[4]: *** [Makefile:1482: all-recursive] Error 1
gmake[4]: Leaving directory 
'/ram/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/bootstrap/kmk'

gmake[3]: *** [Makefile:650: all] Error 2

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

2013-12-23 Thread José García Juanino
On 23 December 2013 08:36, Bernhard Fröhlich de...@bluelife.at wrote:

 Am 22.12.2013 21:57 schrieb Dirk Meyer dirk.me...@dinoex.sub.org:
  Opera has an option to pick your poison.
  you can set COMPAT9, which does conflict with virtualbox.

 No it does not conflict anymore. That has been fixed already.

Only a remark: the goal is install emulators/virtualbox-ose-additions and
www/opera on a
VirtualBox FreeBSD 10.0RC2. I have found a workaround:

1- First,  install emulators/virtualbox-ose-additions  with pkgng. Then you
will get /usr/local/lib/gcc46/libstdc++.so.6
installed by lang/gcc port.
2- Install www/opera from ports: cd /usr/ports/www/opera  make install
clean. This trick  works as the port only
check the installation of the libstdc++.so.6; it does not care the which
package installed the library.

Yes, there are some corner cases you need the flexibility of the port
system :-)

Best regards
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

2013-12-23 Thread Bernhard Fröhlich
Am 23.12.2013 11:10 schrieb José García Juanino jjuan...@gmail.com:

 On 23 December 2013 08:36, Bernhard Fröhlich de...@bluelife.at wrote:
 
  Am 22.12.2013 21:57 schrieb Dirk Meyer dirk.me...@dinoex.sub.org:
   Opera has an option to pick your poison.
   you can set COMPAT9, which does conflict with virtualbox.
 
  No it does not conflict anymore. That has been fixed already.

 Only a remark: the goal is install emulators/virtualbox-ose-additions and
www/opera on a
 VirtualBox FreeBSD 10.0RC2. I have found a workaround:

 1- First,  install emulators/virtualbox-ose-additions  with pkgng. Then
you will get /usr/local/lib/gcc46/libstdc++.so.6
 installed by lang/gcc port.
 2- Install www/opera from ports: cd /usr/ports/www/opera  make install
clean. This trick  works as the port only
 check the installation of the libstdc++.so.6; it does not care the which
package installed the library.

 Yes, there are some corner cases you need the flexibility of the port
system :-)

 Best regards

Yeah, that should work fine and my proposal was to change opera to depend
on lang/gcc instead of lang/gcc46 because it is what most ports will use on
FreeBSD 10.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

2013-12-23 Thread Jung-uk Kim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2013-12-23 05:10:05 -0500, José García Juanino wrote:
 On 23 December 2013 08:36, Bernhard Fröhlich de...@bluelife.at
 wrote:
 
 Am 22.12.2013 21:57 schrieb Dirk Meyer
 dirk.me...@dinoex.sub.org:
 Opera has an option to pick your poison. you can set COMPAT9,
 which does conflict with virtualbox.
 
 No it does not conflict anymore. That has been fixed already.
 
 Only a remark: the goal is install
 emulators/virtualbox-ose-additions and www/opera on a VirtualBox
 FreeBSD 10.0RC2. I have found a workaround:
 
 1- First,  install emulators/virtualbox-ose-additions  with pkgng.
 Then you will get /usr/local/lib/gcc46/libstdc++.so.6 installed by
 lang/gcc port. 2- Install www/opera from ports: cd
 /usr/ports/www/opera  make install clean. This trick  works as
 the port only check the installation of the libstdc++.so.6; it does
 not care the which package installed the library.
 
 Yes, there are some corner cases you need the flexibility of the
 port system :-)

emulators/virtualbox-ose-additions can be built with clang and used
with libc++ just fine.  All you need is the following patches:

https://redports.org/browser/jkim/emulators/virtualbox-ose-additions/files/extrapatch-src-VBox-Additions-x11-VBoxClient-Makefile.kmk
https://redports.org/browser/jkim/emulators/virtualbox-ose-additions/files/extrapatch-src-VBox-Additions-x11-vboxvideo-Makefile.kmk

The port maintainers did not like them, though. :-(

Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)

iQEcBAEBAgAGBQJSuKIoAAoJEHyflib82/FGWFIH/jhBXA+qslegHzE7ikNGSK2z
FajfbU+uHi0TygtGoQxgg8O0lDWbTvUFOtzL6+h+AgE0vjg1QmaUxkl8AUfwi/oi
1SViTxr/hEVDB/1yq7XbPXCkZxp/3UKiQST2/i8kTrIXnGbGgI3BcgrcDNsGRiqL
+43lvKieI1DfIX7Zpi3hunABYTLRTX41BSimv/8XwCfdEgd/w2IMRvj+FKWAQ337
2O8slnkhIIm3fqQgKPzJRNdZb38OdCu8Mc+GSSVMsft/MC1Kb1AgHWqJabAmewz3
icy7d40BbCPrzRrj6KGndqI9VDQJdWF6yNFHsv6RTxZH7JttignBL0txlFs5a/Q=
=9wdZ
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

2013-12-22 Thread Bernhard Fröhlich
Am 22.12.2013 12:13 schrieb José García Juanino jjuan...@gmail.com:

 Hello,

 I have running a recent FreeBSD 10.0-RC2, and I get the following
scenario:

 www/opera depends on lang/gcc46
 devel/kBuild depends on lang/gcc

 But both gcc46 and gcc are incompatible, so I cannot install opera and
 kBuild. However, lang/gcc and lang/gcc46 install the same versión compiler
 4.6.4. Any idea to fix this conflict? I am using  pkgng to install the
 ports.

kBuild is using USE_GCC=yes which uses lang/gcc right now in version 4.6.

Opera has a strict dependency on on FreeBSD 10 for gcc4.6 because of
libstdc++.so.6.

RUN_DEPENDS+=   ${LOCALBASE}/lib/gcc46/libstdc++.so.6:${PORTSDIR}/lang/gcc46

I am not sure if opera really needs to be that strict on which libstdc++ it
uses since it also seems to be happy with libstdc++ from gcc 4.2 on FreeBSD
9.

I've cc'd the opera maintainer so let's see what he thinks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Re: kBuild and opera will not install in 10.0: lang/gcc46 conflicts with lang/gcc

2013-12-22 Thread Bernhard Fröhlich
Am 22.12.2013 21:57 schrieb Dirk Meyer dirk.me...@dinoex.sub.org:

 Bernhard Fröhlich schrieb:,

  Am 22.12.2013 12:13 schrieb Jos=E9 Garc=EDa Juanino 
jjuan...@gmail.com:
   I have running a recent FreeBSD 10.0-RC2, and I get the following
  scenario:
  
   www/opera depends on lang/gcc46
   devel/kBuild depends on lang/gcc
  
   But both gcc46 and gcc are incompatible, so I cannot install opera and
   kBuild. However, lang/gcc and lang/gcc46 install the same versi=F3n
compi=
  ler
   4.6.4. Any idea to fix this conflict? I am using  pkgng to install the
   ports.
 
  kBuild is using USE_GCC=3Dyes which uses lang/gcc right now in version
4.6.
 
  Opera has a strict dependency on on FreeBSD 10 for gcc4.6 because of
  libstdc++.so.6.

 In C++ you can not reuse your libraries without recompilation.
 This breaks the goal of object oriented design as stated in several books.

Why does opera work fine with libstdc++ from gcc 4.2 then?

 Opera has an option to pick your poison.
 you can set COMPAT9, which does conflict with virtualbox.

No it does not conflict anymore. That has been fixed already.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


issues with update databases/py-sqlite3 and devel/kBuild

2013-05-29 Thread Waitman Gobble

Hi,

on a current, updated machine ..

When I try to install databases/py-sqlite3 it bombs out.

using clang. (similar/same results with gcc/gcc46)

 make
===   py27-sqlite3-2.7.5_3 depends on file: /usr/local/bin/python2.7 -
found
===   py27-sqlite3-2.7.5_3 depends on shared library: sqlite3 - found
===  Configuring for py27-sqlite3-2.7.5_3
===   FreeBSD 10 autotools fix applied to
/usr/ports/databases/py-sqlite3/work/Python-2.7.5/Modules/_ctypes/libffi/aclocal.m4
===   FreeBSD 10 autotools fix applied to
/usr/ports/databases/py-sqlite3/work/Python-2.7.5/Modules/_ctypes/libffi/acinclude.m4
===   FreeBSD 10 autotools fix applied to
/usr/ports/databases/py-sqlite3/work/Python-2.7.5/Modules/_ctypes/libffi/m4/libtool.m4
===   FreeBSD 10 autotools fix applied to
/usr/ports/databases/py-sqlite3/work/Python-2.7.5/Modules/_ctypes/libffi/configure
===   FreeBSD 10 autotools fix applied to
/usr/ports/databases/py-sqlite3/work/Python-2.7.5/Modules/zlib/configure
===   FreeBSD 10 autotools fix applied to
/usr/ports/databases/py-sqlite3/work/Python-2.7.5/configure
running config
*** Signal 10

Stop.
make: stopped in /usr/ports/databases/py-sqlite3

 dmesg
pid 88350 (python2.7), uid 0: exited on signal 10 (core dumped)


I'm running 10.0-CURRENT r25: Wed May 29 16:44:31 PDT 2013
ports tree updated to latest, #319402, updated using portmaster. pkg version
shows everything up to date, pkg_libchk shows no issues.


Also,

in devel/kBuild

...
kBuild: Compiling kmkmissing -
/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/kmkbuiltin/err.c
kBuild: Compiling kmkmissing -
/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/kmkbuiltin/fts.c
kBuild: Compiling kmkmissing -
/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/kmkbuiltin/setmode.c
kBuild: Compiling kmkmissing -
/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/kmkbuiltin/strmode.c
kBuild: Compiling kmkmissing -
/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/kmkbuiltin/kbuild_version.c
cc1: error: to generate dependencies you must specify either -M or -MM
kmk: ***
[/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/kUtil/crc32.o]
 Error 1
The failing command:
@gcc -c -O2 -g -O3 -m64 -I/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib
-I/usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/kmk/glob
-I/usr/local/include -DKBUILD_VERSION_MAJOR=0 -DKBUILD_VERSION_MINOR=1
-DKBUILD_VERSION_PATCH=9998 -DKBUILD_OS_FREEBSD -DKBUILD_ARCH_AMD64 -DNDEBUG
-Wp,-MD,/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/kUtil/crc32.o.dep
 
-Wp,-MT,/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/kUtil/crc32.o
 -Wp,-MP -o 
/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/kUtil/crc32.o
 /usr/ports/devel/kBuild/work/kBuild-0.1.9998/src/lib/crc32.c
cc1: error: to generate dependencies you must specify either -M or -MM
kmk: ***
[/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/kmkmissing/kmkbuiltin/setmode.o]
 Error 1
cc1: error: to generate dependencies you must specify either -M or -MM
kmk: ***
[/usr/ports/devel/kBuild/work/kBuild-0.1.9998/out/freebsd.amd64/release/obj/kmkmissing/kmkbuiltin/fts.o]
 Error 1

...there is this closed pr:

status = closed
postdate = 2013-05-19
pr = ports/178767
who = vbox
desc = [PATCH] devel/kBuild: fix build on -CURRENT
last_activity = 2013-05-19
num_msgs = 1

#178767 says this was fixed... (i believe it's talking about the same
problem??).


Anyway, if anyone has some tips or pointers that would be great.

Thank you,

--
Waitman Gobble
San Jose California USA
+1.5108307875


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


kbuild

2008-12-21 Thread Desmond Chapman

I'd like to transfer this port g...@gahr.ch for maintaining. 

_
It’s the same Hotmail®. If by “same” you mean up to 70% faster.
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_broad1_122008___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


virtualbox kBuild security

2008-10-14 Thread Desmond Chapman






http://www.virtualbox.org/ticket/1499

http://wiki.archlinux.org/index.php/VirtualBox#Getting_USB_to_work_in_the_guest_machine

Even though these issues relate to Linux hosts, I have had the same results 
while trying to build on FreeBSD. That which applies the PUEL release also 
applies to the OSE release.




This problem still exists for FreeBSD amd64 when building VBox current.
kBuild is still a security risk due to it changing permissions without the 
users consent. 
The developers have not stated if the qemu code used in vbox is current with 
that used in FreeBSD nor if the networking and image options- qemu related- 
needed to work on FreeBSD amd64 current have been added. 

Please do not reply to this message.










_
Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]


kBuild port

2008-10-11 Thread Desmond Chapman

I'm stepping into this blindly because I want virtualbox to work on freebsd 7.0 
and above amd64.
I need help such as tutorials on Makefiles: building and changing them.

problems: marked as broken. This needs to be changed and a warning needs to be 
issued before installing. Maybe a yes/no prompt added?

I also want to help with the vbox kernel mode. I can do the testing environment.

_
See how Windows connects the people, information, and fun that are part of your 
life.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093175mrt/direct/01/___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]