[OpenIndiana-discuss] Using OI-userland to develop software

[Jim Klimov]

25 июня 2015 г. 6:35:53 CEST, bentahyr at chez.com пишет:
>Merci Aurélien,
>
>Thanks for the explanations. I found a way to get what I wanted, now I
>can start the real thing and I fell into something quite interesting.
>
>------- output ----------
>During compilation of code I fall onto the error :
>/usr/include/signal.h:144:1: error: unknown type name ‘sigset_t’
>extern int sigwait(const sigset_t *_RESTRICT_KYWD, int
>*_RESTRICT_KYWD);
>^                                                                      
>    
>------- end--------------
>
>Which is strange as sigset_t is defined in /usr/include/sys/signal.h
>which is include at the begining of /usr/include/signal.h
>So I'm not sure it doesn't pickup the def as I would expect error in my
>code not in between /usr/include/signal.h and /usr/include/sys/signal.h
>
>I have to admit to go back to C/C++ after more than 15 years makes me
>feel my brain is in concrete.
>
>Best regards.
>Ben
>
>----- Mail original -----
>De: "Aurélien Larcher" <aurelien.larcher at gmail.com>
>À: "Discussion list for OpenIndiana"
><openindiana-discuss at openindiana.org>
>Envoyé: Lundi 22 Juin 2015 11:53:58
>Objet: Re: [OpenIndiana-discuss] Using OI-userland to develop software
>
>Dear Ben,
>
>1) Glib being based on Autotools the relevant "recipes" are in this
>file:
>
>https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/make-rules/configure.mk
>
>As you see, changing the value of COMPONENT_PREFIX to /opt/local in
>your
>glib Makefile will achieve what you want.
>
>2) Instead of getting root to install the package to the local
>repository,
>you can consider giving software installation credentials to your user,
>change the line in /etc/user_attr:
>
>user::::type=normal;profiles=Software Installation
>
>Best
>
>Aurelien
>
>
>
>On Mon, Jun 22, 2015 at 1:39 AM, <bentahyr at chez.com> wrote:
>
>> Hi,
>>
>> I'm trying to use oi-userland on hipster.
>> The current config I set up is :
>> - main repository host is 151a9 exporting oi-userland
>> - work is done on hipster virtual machines powered by VirtualBox and
>> mounting the oi-userland from host by NFS
>>
>> As an example I'm trying to work on software requiring a more recent
>glib
>> than what's on hipster (v2.28.8) and oi-userland seems to be able to
>> provide v2.43.4.
>> I followed the wiki and am able to build the glib, no issue there.
>> I'm stuck at next stage.
>> I would like to use it in a another directory, like /opt/local/req.
>> I tried to change the PROTO_DIR variable but it doesn't seem to be
>the way
>> to do it.
>> I tried to publish but I need to be root to pkgsend nd of course, I
>have
>> root_squash on NFS export from hosts.
>>
>> What would be the canonical way to do things ?
>> Should I create an entry (directory and makefile, and...) for my
>software
>> in oi-userland ?
>> Should I just get to apply the patches and make clean, autogen with
>> different prefix in glib-2.43.4 subdirectory ?
>>
>> Best regards.
>> Ben
>>
>> _______________________________________________
>> openindiana-discuss mailing list
>> openindiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
>-- 
>-------------------------------------------------------------------------------
>LARCHER Aurélien          | KTH, School of Computer Science and
>Communication
>Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 4, 100 44
>Stockholm,
>SWEDEN
>-------------------------------------------------------------------------------
>_______________________________________________
>openindiana-discuss mailing list
>openindiana-discuss at openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss
>
>_______________________________________________
>openindiana-discuss mailing list
>openindiana-discuss at openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss

Try to retrace ifdef macros relevant to that definition, and that you don't have same filenames in more preferred include-paths.

Looking at very verbose make output (gmake -d --trace V=1 ...) and preprocessor output (gcc -e IIRC) can help.

HTH, Jim
--
Typos courtesy of K-9 Mail on my Samsung Android