Help building Kos 2.0/Dc-chain

If you have any questions on programming, this is the place to ask them, whether you're a newbie or an experienced programmer. Discussion on programming in general is also welcome. We will help you with programming homework, but we will not do your work for you! Any porting requests must be made in Developmental Ideas.
User avatar
BlueCrab
The Crabby Overlord
The Crabby Overlord
Posts: 5387
Joined: Mon May 27, 2002 11:31 am
Location: Sailing the Skies of Arcadia
Has liked: 1 time
Been liked: 12 times
Contact:

Re: Help building Kos 2.0/Dc-chain

Post by BlueCrab » Thu Aug 18, 2016 6:42 pm

Hrm... It actually looks like Newlib built and installed fine, oddly enough. I guess the next thing to look at is the GCC pass 2 log?
User avatar
bogglez
Moderator
Moderator
Posts: 576
Joined: Sun Apr 20, 2014 9:45 am
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by bogglez » Thu Aug 18, 2016 7:02 pm

ThePerfectK wrote:thinking about it, you'll need to edit your environ.sh script to point to the correct KOS path. It shouldn't be hard to whip up a program that will search environ.sh and replace that path with a string of our choosing, but it sort of complicates the automation process. I'm guessing this should be a compiled executable program rather than a batch file instead.

Same question applies, though - is there a way to manipulate Cygwin from a command line?
Just leave the standard path /opt/toolchains/dc. If you want to change some variables you can output the file using sed toward the target destination.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
User avatar
ThePerfectK
DCEmu Freak
DCEmu Freak
Posts: 94
Joined: Thu Apr 27, 2006 10:15 am
Has liked: 6 times
Been liked: 13 times

Re: Help building Kos 2.0/Dc-chain

Post by ThePerfectK » Thu Aug 18, 2016 8:30 pm

bogglez wrote:
ThePerfectK wrote:thinking about it, you'll need to edit your environ.sh script to point to the correct KOS path. It shouldn't be hard to whip up a program that will search environ.sh and replace that path with a string of our choosing, but it sort of complicates the automation process. I'm guessing this should be a compiled executable program rather than a batch file instead.

Same question applies, though - is there a way to manipulate Cygwin from a command line?
Just leave the standard path /opt/toolchains/dc. If you want to change some variables you can output the file using sed toward the target destination.
Got it, I'm helping someone in the IRC right now with this right now, so I'll give it a hand.
Still Thinking!~~
User avatar
ThePerfectK
DCEmu Freak
DCEmu Freak
Posts: 94
Joined: Thu Apr 27, 2006 10:15 am
Has liked: 6 times
Been liked: 13 times

Re: Help building Kos 2.0/Dc-chain

Post by ThePerfectK » Thu Aug 18, 2016 9:14 pm

Am I missing any packages to install?

Code: Select all

libgmp-dev
libmpfr-dev
libmpc-dev
gettext
wget
libelf-dev
texinfo
bison
flex
sed
make
tar
bzip2
patch
gawk
git
gcc
g++
?
Still Thinking!~~
User avatar
BlueCrab
The Crabby Overlord
The Crabby Overlord
Posts: 5387
Joined: Mon May 27, 2002 11:31 am
Location: Sailing the Skies of Arcadia
Has liked: 1 time
Been liked: 12 times
Contact:

Re: Help building Kos 2.0/Dc-chain

Post by BlueCrab » Thu Aug 18, 2016 10:14 pm

Here's the list for Debian:
gawk patch bzip2 tar make libgmp-dev libmpfr-dev libmpc-dev gettext wget libelf-dev texinfo bison flex sed git build-essential diffutils curl python subversion libjpeg-dev libpng-dev
frozenbinarystudio
DCEmu Cool Newbie
DCEmu Cool Newbie
Posts: 13
Joined: Wed Aug 17, 2016 2:01 pm
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by frozenbinarystudio » Sun Aug 21, 2016 10:19 am

BlueCrab wrote:Hrm... It actually looks like Newlib built and installed fine, oddly enough. I guess the next thing to look at is the GCC pass 2 log?
Yes indeed you can! I assumed you meant the sh-elf log as its the only one marked as 2nd pass for GCC

Here are the last lines in the log. Full file below!

Code: Select all

../../gcc-4.7.3/gcc/cp/typeck.c:2592:4: note: in expansion of macro ‘gcc_assert’
    gcc_assert (CLASS_TYPE_P (scope));
    ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:2593:4: note: in expansion of macro ‘gcc_assert’
    gcc_assert (TREE_CODE (name) == IDENTIFIER_NODE
    ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘build_ptrmemfunc_access_expr’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:2699:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TYPE_PTRMEMFUNC_P (ptrmem_type));
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cp_build_indirect_ref’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:2833:12: note: in expansion of macro ‘gcc_unreachable’
            gcc_unreachable ();
            ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘get_member_function_from_ptrfunc’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:3101:4: note: in expansion of macro ‘gcc_unreachable’
    gcc_unreachable ();
    ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘build_function_call_vec’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:3183:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (params == orig_params);
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cp_build_binary_op’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:4221:4: note: in expansion of macro ‘gcc_assert’
    gcc_assert (!TYPE_PTRMEMFUNC_P (type0)
    ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:4224:4: note: in expansion of macro ‘gcc_assert’
    gcc_assert (!TYPE_PTRMEMFUNC_P (type1)
    ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:4428:5: note: in expansion of macro ‘gcc_unreachable’
     gcc_unreachable();
     ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:4450:5: note: in expansion of macro ‘gcc_unreachable’
     gcc_unreachable();
     ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cp_build_addr_expr_1’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:4806:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (arg) != IDENTIFIER_NODE
   ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:4976:2: note: in expansion of macro ‘gcc_assert’
  gcc_assert (PTRMEM_OK_P (arg));
  ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:5013:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (TREE_CODE (fn) == FUNCTION_DECL
       ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:5033:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (same_type_ignoring_top_level_qualifiers_p
       ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cxx_mark_addressable’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:5480:2: note: in expansion of macro ‘gcc_assert’
  gcc_assert (DECL_LANG_SPECIFIC (x) == 0
  ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘build_x_compound_expr_from_list’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:5603:6: note: in expansion of macro ‘gcc_unreachable’
      gcc_unreachable ();
      ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘check_for_casting_away_constness’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:5756:7: note: in expansion of macro ‘gcc_unreachable’
       gcc_unreachable();
       ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘convert_member_func_to_ptr’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6110:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TYPE_PTRMEMFUNC_P (intype)
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘build_const_cast_1’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6350:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (dst_type != error_mark_node);
   ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6353:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (!processing_template_decl);
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cp_build_c_cast’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6610:4: note: in expansion of macro ‘gcc_assert’
    gcc_assert (valid_p);
    ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cp_build_modify_expr’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6693:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (!TREE_SIDE_EFFECTS (TREE_OPERAND (lhs, 0))
       ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6814:4: note: in expansion of macro ‘gcc_assert’
    gcc_assert (!((TREE_CODE (lhstype) == REFERENCE_TYPE
    ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6854:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (TREE_CODE (lhstype) != REFERENCE_TYPE);
       ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:6855:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (TREE_CODE (TREE_TYPE (newrhs)) != REFERENCE_TYPE);
       ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘build_ptrmemfunc’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:7235:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert  (same_type_ignoring_top_level_qualifiers_p
       ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:7259:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (fn) == FUNCTION_DECL
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘expand_ptrmemfunc_cst’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:7280:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (fn) == FUNCTION_DECL);
   ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:7331:4: note: in expansion of macro ‘gcc_unreachable’
    gcc_unreachable ();
    ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘convert_for_assignment’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:7511:9: note: in expansion of macro ‘gcc_unreachable’
         gcc_unreachable();
         ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:7558:8: note: in expansion of macro ‘gcc_unreachable’
        gcc_unreachable();
        ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘check_return_expr’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:7818:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (valtype != NULL_TREE);
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cp_type_quals’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:8206:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert ((TREE_CODE (type) != METHOD_TYPE
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘type_memfn_quals’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/typeck.c:8224:5: note: in expansion of macro ‘gcc_unreachable’
     gcc_unreachable ();
     ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘apply_memfn_quals’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:8234:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (type) == FUNCTION_TYPE);
   ^
../../gcc-4.7.3/gcc/cp/typeck.c: In function ‘cp_apply_type_quals_to_decl’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/typeck.c:8286:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (!(TREE_CODE (type) == FUNCTION_TYPE
   ^
gcc -c  -DIN_GCC_FRONTEND -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat   -DHAVE_CONFIG_H -I. -Icp -I../../gcc-4.7.3/gcc -I../../gcc-4.7.3/gcc/cp -I../../gcc-4.7.3/gcc/../include -I../../gcc-4.7.3/gcc/../libcpp/include  -I../../gcc-4.7.3/gcc/../libdecnumber -I../../gcc-4.7.3/gcc/../libdecnumber/dpd -I../libdecnumber    ../../gcc-4.7.3/gcc/cp/cvt.c -o cp/cvt.o
In file included from ../../gcc-4.7.3/gcc/cp/cvt.c:33:0:
../../gcc-4.7.3/gcc/tree.h:3277:11: warning: identifier ‘thread_local’ conflicts with C++ keyword [-Wc++-compat]
  unsigned thread_local : 1;
           ^
In file included from ../../gcc-4.7.3/gcc/cp/cvt.c:30:0:
../../gcc-4.7.3/gcc/tree.h: In function ‘tree_low_cst’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/tree.h:4435:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (host_integerp (t, pos));
   ^
../../gcc-4.7.3/gcc/tree.h: In function ‘function_args_iter_next’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/tree.h:5143:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (i->next != NULL_TREE);
   ^
In file included from ../../gcc-4.7.3/gcc/cp/cvt.c:30:0:
../../gcc-4.7.3/gcc/cp/cp-tree.h: In function ‘type_of_this_parm’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cp-tree.h:4830:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (fntype) == METHOD_TYPE);
   ^
../../gcc-4.7.3/gcc/cp/cvt.c: In function ‘cp_convert_to_pointer’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cvt.c:235:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (GET_MODE_SIZE (TYPE_MODE (TREE_TYPE (expr)))
       ^
../../gcc-4.7.3/gcc/cp/cvt.c: In function ‘build_up_reference’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cvt.c:315:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (type) == REFERENCE_TYPE);
   ^
../../gcc-4.7.3/gcc/cp/cvt.c: In function ‘convert_to_reference’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cvt.c:422:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (intype) != REFERENCE_TYPE);
   ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cvt.c:423:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (reftype) == REFERENCE_TYPE);
   ^
../../gcc-4.7.3/gcc/cp/cvt.c: In function ‘ignore_overflows’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cvt.c:570:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (!TREE_OVERFLOW (orig));
       ^
../../gcc-4.7.3/gcc/cp/cvt.c: In function ‘ocp_convert’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cvt.c:682:4: note: in expansion of macro ‘gcc_assert’
    gcc_assert (!TREE_ADDRESSABLE (type));
    ^
../../gcc-4.7.3/gcc/cp/cvt.c: In function ‘convert_to_void’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/cvt.c:1013:7: note: in expansion of macro ‘gcc_unreachable’
       gcc_unreachable ();
       ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/cvt.c:1057:7: note: in expansion of macro ‘gcc_unreachable’
       gcc_unreachable ();
       ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/cvt.c:1101:7: note: in expansion of macro ‘gcc_unreachable’
       gcc_unreachable ();
       ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/cvt.c:1167:10: note: in expansion of macro ‘gcc_unreachable’
          gcc_unreachable ();
          ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/cvt.c:1280:10: note: in expansion of macro ‘gcc_unreachable’
          gcc_unreachable ();
          ^
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/cvt.c:1326:7: note: in expansion of macro ‘gcc_unreachable’
       gcc_unreachable ();
       ^
gcc -c  -DIN_GCC_FRONTEND -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat   -DHAVE_CONFIG_H -I. -Icp -I../../gcc-4.7.3/gcc -I../../gcc-4.7.3/gcc/cp -I../../gcc-4.7.3/gcc/../include -I../../gcc-4.7.3/gcc/../libcpp/include  -I../../gcc-4.7.3/gcc/../libdecnumber -I../../gcc-4.7.3/gcc/../libdecnumber/dpd -I../libdecnumber    ../../gcc-4.7.3/gcc/cp/except.c -o cp/except.o
In file included from ../../gcc-4.7.3/gcc/cp/except.c:30:0:
../../gcc-4.7.3/gcc/tree.h:3277:11: warning: identifier ‘thread_local’ conflicts with C++ keyword [-Wc++-compat]
  unsigned thread_local : 1;
           ^
In file included from ../../gcc-4.7.3/gcc/cp/except.c:27:0:
../../gcc-4.7.3/gcc/tree.h: In function ‘tree_low_cst’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/tree.h:4435:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (host_integerp (t, pos));
   ^
../../gcc-4.7.3/gcc/tree.h: In function ‘function_args_iter_next’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/tree.h:5143:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (i->next != NULL_TREE);
   ^
In file included from ../../gcc-4.7.3/gcc/cp/except.c:27:0:
../../gcc-4.7.3/gcc/cp/cp-tree.h: In function ‘type_of_this_parm’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/cp-tree.h:4830:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (TREE_CODE (fntype) == METHOD_TYPE);
   ^
../../gcc-4.7.3/gcc/gimple.h: In function ‘extract_ops_from_tree’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/gimple.h:1988:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (op2 == NULL_TREE);
   ^
../../gcc-4.7.3/gcc/cp/except.c: In function ‘choose_personality_routine’:
../../gcc-4.7.3/gcc/system.h:694:61: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
 #define gcc_unreachable() (fancy_abort (__FILE__, __LINE__, __FUNCTION__))
                                                             ^
../../gcc-4.7.3/gcc/cp/except.c:368:7: note: in expansion of macro ‘gcc_unreachable’
       gcc_unreachable ();
       ^
In file included from ../../gcc-4.7.3/gcc/cp/except.c:987:0:
cfns.gperf: At top level:
cfns.gperf:101:1: error: ‘gnu_inline’ attribute present on ‘libc_name_p’
cfns.gperf:26:14: error: but not here
In file included from ../../gcc-4.7.3/gcc/cp/except.c:27:0:
../../gcc-4.7.3/gcc/cp/except.c: In function ‘nothrow_spec_p’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/except.c:1251:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (!DEFERRED_NOEXCEPT_SPEC_P (spec));
   ^
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/except.c:1259:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (processing_template_decl
   ^
../../gcc-4.7.3/gcc/cp/except.c: In function ‘type_noexcept_p’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/except.c:1272:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (!DEFERRED_NOEXCEPT_SPEC_P (spec));
   ^
../../gcc-4.7.3/gcc/cp/except.c: In function ‘type_throw_all_p’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/except.c:1286:3: note: in expansion of macro ‘gcc_assert’
   gcc_assert (!DEFERRED_NOEXCEPT_SPEC_P (spec));
   ^
../../gcc-4.7.3/gcc/cp/except.c: In function ‘build_noexcept_spec’:
../../gcc-4.7.3/gcc/system.h:674:55: warning: ISO C does not support ‘__FUNCTION__’ predefined identifier [-Wpedantic]
    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0 : 0))
                                                       ^
../../gcc-4.7.3/gcc/cp/except.c:1319:7: note: in expansion of macro ‘gcc_assert’
       gcc_assert (processing_template_decl
       ^
make[3]: *** [Makefile:1069: cp/except.o] Error 1
make[3]: Leaving directory '/home/Maple/dc/kos/utils/dc-chain/build-gcc-sh-elf-4.7.3/gcc'
make[2]: *** [Makefile:3853: all-gcc] Error 2
make[2]: Leaving directory '/home/Maple/dc/kos/utils/dc-chain/build-gcc-sh-elf-4.7.3'
make[1]: *** [Makefile:870: all] Error 2
make[1]: Leaving directory '/home/Maple/dc/kos/utils/dc-chain/build-gcc-sh-elf-4.7.3'
Attachments
build-gcc-sh-elf-4.7.3-pass2.log
(391.21 KiB) Downloaded 28 times
User avatar
bogglez
Moderator
Moderator
Posts: 576
Joined: Sun Apr 20, 2014 9:45 am
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by bogglez » Sun Aug 21, 2016 10:26 am

Perhaps this is related. http://unix.stackexchange.com/a/260190

In this thread the same warning was issued and the problem was that a newer gcc version added a new error flag.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
frozenbinarystudio
DCEmu Cool Newbie
DCEmu Cool Newbie
Posts: 13
Joined: Wed Aug 17, 2016 2:01 pm
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by frozenbinarystudio » Sun Aug 21, 2016 10:33 am

bogglez wrote:Perhaps this is related. http://unix.stackexchange.com/a/260190

In this thread the same warning was issued and the problem was that a newer gcc version added a new error flag.
The final line settles it for me
Long story short, I guess you are better off by running a virtual machine or a docker image.
Did I not mention how much of a huge PITA Docker was on Windows?

If this process is similar in being difficult for Win Os I can happily try the VM install method. This may just settle it for me.
User avatar
bogglez
Moderator
Moderator
Posts: 576
Joined: Sun Apr 20, 2014 9:45 am
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by bogglez » Sun Aug 21, 2016 5:45 pm

And this is the other problem (this seems to be causing the actual error).
https://gcc.gnu.org/ml/gcc-patches/2015 ... 00375.html
That sounds similar :-/
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
User avatar
BlueCrab
The Crabby Overlord
The Crabby Overlord
Posts: 5387
Joined: Mon May 27, 2002 11:31 am
Location: Sailing the Skies of Arcadia
Has liked: 1 time
Been liked: 12 times
Contact:

Re: Help building Kos 2.0/Dc-chain

Post by BlueCrab » Sun Aug 21, 2016 11:32 pm

That's probably easy enough to go ahead and add to the patchset... I'll do so when I get a chance.
frozenbinarystudio
DCEmu Cool Newbie
DCEmu Cool Newbie
Posts: 13
Joined: Wed Aug 17, 2016 2:01 pm
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by frozenbinarystudio » Sun Aug 28, 2016 10:51 pm

So I actually got time to make a VM of Ubuntu 16.04 and follow the Linux install steps in bogglez signature. There was a bit of coaxing and a few seemingly random failures but if I read this correctly it appears KOS compiled, if so whoo hoo. It also appears KOS Ports did not compile.

It seems to hang on /kos-ports/zlib. I believe this is because of a hidden folder name .pki being accessible only by the root user. Here are the logs for that issue for your viewing pleasure.

Code: Select all

make[3]: Entering directory '/opt/toolchains/dc/kos/kernel/libc/c11'
cp call_once.o cnd_broadcast.o cnd_destroy.o cnd_init.o cnd_signal.o cnd_timedwait.o cnd_wait.o mtx_destroy.o mtx_init.o mtx_lock.o mtx_timedlock.o mtx_trylock.o mtx_unlock.o thrd_create.o thrd_current.o thrd_detach.o thrd_equal.o thrd_exit.o thrd_join.o thrd_sleep.o thrd_yield.o tss_create.o tss_delete.o tss_get.o tss_set.o aligned_alloc.o /opt/toolchains/dc/kos/kernel/build/
make[3]: Leaving directory '/opt/toolchains/dc/kos/kernel/libc/c11'
make[2]: Leaving directory '/opt/toolchains/dc/kos/kernel/libc'
make -C  exports
make[2]: Entering directory '/opt/toolchains/dc/kos/kernel/exports'
Makefile:18: warning: overriding recipe for target 'clean'
/opt/toolchains/dc/kos/Makefile.prefab:19: warning: ignoring old recipe for target 'clean'
cp nmmgr.o kernel_exports.o exports.o library.o /opt/toolchains/dc/kos/kernel/build/
make[2]: Leaving directory '/opt/toolchains/dc/kos/kernel/exports'
rm -f /opt/toolchains/dc/kos/lib/dreamcast/libkallisti.a
kos-ar rcs /opt/toolchains/dc/kos/lib/dreamcast/libkallisti.a build/*.o
kos-ar rcs /opt/toolchains/dc/kos/lib/dreamcast/libkallisti_exports.a stubs/*.o
make[1]: Leaving directory '/opt/toolchains/dc/kos/kernel'
make[1]: Entering directory '/opt/toolchains/dc/kos/addons'
for i in `ls */kos/dreamcast.cnf | sed -e "s%/kos/dreamcast.cnf%%g"`; do make -C $i || exit -1; done
make[2]: Entering directory '/opt/toolchains/dc/kos/addons/libkosext2fs'
rm -f /opt/toolchains/dc/kos/addons/lib/dreamcast/libkosext2fs.a
/opt/toolchains/dc/sh-elf/bin/sh-elf-ar rcs /opt/toolchains/dc/kos/addons/lib/dreamcast/libkosext2fs.a ext2fs.o bitops.o block.o inode.o superblock.o fs_ext2.o symlink.o directory.o 
make[2]: Leaving directory '/opt/toolchains/dc/kos/addons/libkosext2fs'
make[2]: Entering directory '/opt/toolchains/dc/kos/addons/libkosutils'
rm -f /opt/toolchains/dc/kos/addons/lib/dreamcast/libkosutils.a
/opt/toolchains/dc/sh-elf/bin/sh-elf-ar rcs /opt/toolchains/dc/kos/addons/lib/dreamcast/libkosutils.a bspline.o img.o pcx_small.o md5.o netcfg.o 
make[2]: Leaving directory '/opt/toolchains/dc/kos/addons/libkosutils'
make[2]: Entering directory '/opt/toolchains/dc/kos/addons/libppp'
rm -f /opt/toolchains/dc/kos/addons/lib/dreamcast/libppp.a
/opt/toolchains/dc/sh-elf/bin/sh-elf-ar rcs /opt/toolchains/dc/kos/addons/lib/dreamcast/libppp.a ppp.o lcp.o pap.o ipcp.o ppp_scif.o ppp_modem.o 
make[2]: Leaving directory '/opt/toolchains/dc/kos/addons/libppp'
make[1]: Leaving directory '/opt/toolchains/dc/kos/addons'
Compiling KOS ports.
Checking if /opt/toolchains/dc/kos/../kos-ports/SDL is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/SDL is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libGL is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libGL is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libbz2 is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libbz2 is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libconio is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libconio is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libdcplib is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libdcplib is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libimageload is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libimageload is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libjpeg is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libjpeg is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libkmg is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libkmg is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libkosh is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libkosh is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libmodplug is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libmodplug is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libmp3 is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libmp3 is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libogg is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libogg is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/liboggvorbisplay is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/liboggvorbisplay is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libopusplay is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libopusplay is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libparallax is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libparallax is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libpcx is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libpcx is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libpng is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libpng is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libtga is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libtga is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libtremor is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libtremor is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libtsunami is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libtsunami is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/libvorbis is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/libvorbis is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/lua is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/lua is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/opus is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/opus is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/opusfile is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/opusfile is already installed and up-to-date. Skipping.
Checking if /opt/toolchains/dc/kos/../kos-ports/zlib is installed and up-to-date...
/opt/toolchains/dc/kos/../kos-ports/zlib is already installed and up-to-date. Skipping.
User avatar
bogglez
Moderator
Moderator
Posts: 576
Joined: Sun Apr 20, 2014 9:45 am
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by bogglez » Mon Aug 29, 2016 5:18 am

Looking at https://github.com/ljsebald/kos-ports/tree/master/zlib there's no pki folder in the repository and I've never had that issue in the past.
Did you perhaps cd into that folder and run some commands as root? I believe Ubuntu might generate pki folders since it's related to private keys for cryptography.

That said the setup seems to have worked.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
frozenbinarystudio
DCEmu Cool Newbie
DCEmu Cool Newbie
Posts: 13
Joined: Wed Aug 17, 2016 2:01 pm
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by frozenbinarystudio » Mon Aug 29, 2016 11:13 am

bogglez wrote:Looking at https://github.com/ljsebald/kos-ports/tree/master/zlib there's no pki folder in the repository and I've never had that issue in the past.
Did you perhaps cd into that folder and run some commands as root? I believe Ubuntu might generate pki folders since it's related to private keys for cryptography.

That said the setup seems to have worked.
I did not actually run any commands except the one from the install script you wrote. This appears to be part of that process. Every time I do

Code: Select all

sudo rm -r ~/.pki
it is recreated once I back to the part the build hangs at.

The .pki file does appear to be one of those hidden config folders some programs create, such as Mavens .m2 folder or Gits .git folder.

I have attempted to change permissions on the folder with

Code: Select all

sudo chmod -R 777 ~/.pki
but the same hangup happens.

I will start over again tonight and get the specific error it printed to the console. Something about error creating the directory, when it was already created.

Edit: This is the same error I get, but on a different line. Same thing it complains about though.

Code: Select all

[9451:0914/145041:ERROR:nss_util.cc(97)] Failed to create /home/user/.pki/nssdb directory.
I found this when I was looking up this issue last night and spaced it. Here is the link to that particular issue.

https://github.com/electron/electron/issues/2778

Thanks!
User avatar
bogglez
Moderator
Moderator
Posts: 576
Joined: Sun Apr 20, 2014 9:45 am
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by bogglez » Mon Aug 29, 2016 11:36 am

Seems like selinux in Ubuntu is misconfigured. There are some commands in the last few posts of the issue you posted which might help, I don't use Ubuntu or selinux so I can't test them, sorry.

If it's any help, your kos is ready to be used. The ports are all optional, so if you don't use the ones that didn't build in your code it won't matter for you.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
frozenbinarystudio
DCEmu Cool Newbie
DCEmu Cool Newbie
Posts: 13
Joined: Wed Aug 17, 2016 2:01 pm
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by frozenbinarystudio » Wed Aug 31, 2016 1:49 pm

Thanks very much for the help! I will see about resolving the issue with misconfiguration. I would still like the ports to build so I can into that too. Having all the help I could get is awesome I think.

I also noticed you updated the wiki with your script to make it easier to find. Thanks for that I have now bookmarked it.

I look forward to learning how this all works now! So excited!
frozenbinarystudio
DCEmu Cool Newbie
DCEmu Cool Newbie
Posts: 13
Joined: Wed Aug 17, 2016 2:01 pm
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by frozenbinarystudio » Tue Sep 06, 2016 10:27 pm

bogglez wrote:Seems like selinux in Ubuntu is misconfigured. There are some commands in the last few posts of the issue you posted which might help, I don't use Ubuntu or selinux so I can't test them, sorry.


This appears to not be the case as I do not have selinux installed. Not only does calling the command from the terminal state it is not installed, but according to the following post, it is not even recommended for later favors of Unbuntu due to being horribly borked.

Running chown on the .pki folder seems to return the error where it cannot create the nssdb directory... even though it exists.

I wish I knew what was calling nss_util.cc...

http://askubuntu.com/questions/481293/s ... -in-ubuntu
bogglez wrote:If it's any help, your kos is ready to be used. The ports are all optional, so if you don't use the ones that didn't build in your code it won't matter for you.
Which ones are the most recommended for newbs? I ask because if one of the ports is boned I will just adjust the script to skip it entirely. I also ask as Zlib seems to have installed, I am actually not sure WHY it is hanging now.

Sorry to be keep bringing this up. I just really want to get stuck in!!!!

EDIT: Silly question, but do the ports build in the alphabetical order of the directory structure? I ask because if that is the case, and Zlib is in fact skipping over due to being built, then ports might have installed and the script is just hanging about. Weird but if that is the case I will take it!

ALSO EDIT: Thought about this one. I had to run the kos-setup.sh as sudo, as it complained about recipes not working without it. Could this be related? Sorry. I really hate mysteries!
Disregard!

It seems the culprit wasn't anything to do with Kos or ports...

It was this line in your script bogglez:

Code: Select all

program_exists x-www-browser && x-www-browser 'http://gamedev.allusion.net/docs/kos-current/structcont__state__t.html'
Commenting it out made the whole install run without a hitch! I am up and running.

Thank you for your patience. I am terribly sorry to be annoying with questions and problems. As I said, I am very eager to get into this!
User avatar
bogglez
Moderator
Moderator
Posts: 576
Joined: Sun Apr 20, 2014 9:45 am
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by bogglez » Wed Sep 07, 2016 5:26 am

sudo should not be required.
My guess is that it runs the web browser as root and that's what caused all the problems. I'll try the script again on a Debian computer which is somewhat similar to Ubuntu.

All ports are optional. Png, jpg, zlib support are useful for many, but you should not be using png and jpg on Dreamcast anyway, in my opinion (use pvr format from the tutorials instead).
Zlib is something you need to add in your code. Just compiling the port will do nothing, it will just make the library available for use.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
User avatar
bogglez
Moderator
Moderator
Posts: 576
Joined: Sun Apr 20, 2014 9:45 am
Has liked: 0
Been liked: 0

Re: Help building Kos 2.0/Dc-chain

Post by bogglez » Wed Sep 07, 2016 7:17 am

Made two changes to the script:
- Disallow root. The script should be run as sh kos_setup_script.sh
- Check for required software at start, to save people from bad surprises later (I was missing makeinfo on my fresh Debian machine..).

It seems your issue is (mostly?) solved, but if you could run the following for me using the new script and upload the output, I'd be able to debug any remaining issues.

Code: Select all

sudo mv /opt/toolchains /opt/toolchains_backup
sh kos_setup_script.sh &> kos_setup_log.txt
This redirects normal output and error output to a log file.
Wiki & tutorials: http://dcemulation.org/?title=Development
Wiki feedback: viewtopic.php?f=29&t=103940
My libgl playground (not for production): https://bitbucket.org/bogglez/libgl15
My lxdream fork (with small fixes): https://bitbucket.org/bogglez/lxdream
Post Reply