Yeah, I'm using trunk Here's the output from running make in the SystemConfig
directory:

Making build-headers in subprojects of framework SystemConfig...
make[1]: Entering directory
`/var/abs/local/etoile-svn/src/etoile-build/Etoile/Frameworks/SystemConfig/Source'
Making build-headers for subproject libSystemConfig...
make[2]: Nothing to be done for `internal-subproject-build-headers'.
make[1]: Leaving directory
`/var/abs/local/etoile-svn/src/etoile-build/Etoile/Frameworks/SystemConfig/Source'
Making build-headers for framework SystemConfig...
Making all in subprojects of framework SystemConfig...
make[1]: Entering directory
`/var/abs/local/etoile-svn/src/etoile-build/Etoile/Frameworks/SystemConfig/Source'
Making all for subproject libSystemConfig...
 Compiling file SCConfig.m ...
In file included from /usr/include/sys/errno.h:1,
                 from /usr/include/sys/errno.h:1,
                 from /usr/include/sys/errno.h:1,
----------Snip, same line outputted many times---------------
                 from /usr/include/sys/errno.h:1,
                 from
/opt/GNUstep/System/Library/Headers/Foundation/NSDebug.h:31,
                 from
/opt/GNUstep/System/Library/Headers/Foundation/Foundation.h:35,
                 from SCConfig.m:27:
/usr/include/sys/errno.h:1:19: error: #include nested too deeply
make[2]: *** [obj/SCConfig.o] Error 1
make[1]: *** [libSystemConfig.all.subproject.variables] Error 2
make[1]: Leaving directory
`/var/abs/local/etoile-svn/src/etoile-build/Etoile/Frameworks/SystemConfig/Source'
make: *** [SystemConfig.all.framework.variables] Error 2



Hi,

I'm looking at this problem right now but I haven't figured it out yet.

Le 21 nov. 07 à 21:07, dustin_mays a écrit :

> gnustep-make: SVN rev. 25566
> gnustep-base: SVN rev. 25576
> gnustep-back: SVN rev. 25575
> gnustep-gui: SVN rev. 25594
>
> These are all current as of two days ago. I'm including the ls -l  
> build
> output as an attachment because it's really, really long.
> http://www.nabble.com/file/p13885020/lslbuild-output lslbuild-output

SystemConfig is missing in the output of the Build directory. It means  
that either SystemConfig hasn't been compiled or hasn't been exported  
in Build directory. For this last case, this would imply that  
etoile.make rules weren't properly invoked when 'make' compiles / 
Frameworks/SystemConfig.
If there is a directory SystemConfig.framework in Frameworks/ 
SystemConfig, it means the framework compiled as expected. If it is  
the case, you may try to cd into /Frameworks/SystemConfig, then type  
'make' to see whether the Build directory is modified or not by doing  
that. If SystemConfig is properly exported, you should have the three  
following links in Build:
SystemConfig (header dir)
libSystemConfig.so (lib file)
SystemConfig.framework (framework dir)
-- 
View this message in context: 
http://www.nabble.com/Hardware.app-compiling-problems-on-Arch-tf4847499.html#a13979135
Sent from the Etoile - Dev mailing list archive at Nabble.com.


_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev

Reply via email to