Visit The New, Modern Unix Linux Community

Operating Systems Linux SuSE g++ build on SUSE 12.1, cannot open included file Post 302581725 by LMHmedchem on Wednesday 14th of December 2011 12:14:11 AM
Well I got it hacked, more or less. The problem was the the first include statement was in a file in a different sub directory than the included file. The included was done as,
      INCLUDE '../src_client_main/PARAM.DAT'

Within the included PARAM.DAT file, there was the regular include I listed above. I guess it looks like,
./src_models/MODELS.FOR (INCLUDE '../src_client_main/PARAM.DAT')
./src_client_main/PARAM.DAT, MOLERRORS.DAT

PARAM.DAT has the INCLUDE 'MOLERRORS.DAT' in it. When the pre-processer was working on MODELS.FOR, it was able to find PARAM.DAT when referenced with that kind of path, but it didn't look for MOLERRORS.DAT with the ../src_client_main/ path. I guess it just looked for ./MOLERRORS.DAT and didn't find it. This setup works under cygwin, ubuntu, and cent, so I am surprised there is a difference with suse. I think it's all the same gcc stuff, but I guess I should look into it. It runs quite a bit slower under suse, so maybe not.

I guess I need to investigate a better way to set up my src structure. I have files in a few different sub folders, but there are some dependencies that need to be included from several places. I'm not sure how to address that without doing something lame like having several copies of the included files. It seems like there was a way to list the dependencies in the make file and include them on the compile line instead of explicitly in the src file, but I'm not sure about that.

Test Your Knowledge in Computers #475
Difficulty: Medium
A Yottabyte (YB) equals 1,208,925,819,614,629,174,706,176 bytes.
True or False?

9 More Discussions You Might Find Interesting

1. Programming

Open Suse 10 seg fault

Okay, so here is some code that when compiled on Fedora Core 6 works great, but when I compile and run it on OpenSuse 10 it gives back a seg fault when trying to join the 2nd thead. #include <pthread.h> #include <stdio.h> int print_message_function( void *ptr ); int x = 1; main() { ... (1 Reply)
Discussion started by: chrisdrobison
1 Replies

2. SuSE

open SUSE 11.0 and its printer configuration

Does anybody who uses open SUSE 11.0? I have used open SUSE 10.2 for about 18 months. Today I installed open SUSE 11.0 The printer does not work. I tried all the tricks tweak it. My printer is an old one. It is HP Deskjet 5600 series. It works fine. I did the configuration using... (0 Replies)
Discussion started by: Angelo
0 Replies

3. Red Hat

cannot set user id: Resource temporarily unavailable (not open file/open process related)

First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting. First, this is what's running: This is the error when jobs are run or the... (0 Replies)
Discussion started by: Katahdin
0 Replies

4. UNIX for Advanced & Expert Users

PATH included in .o file of device driver

Hello friends, I am building one driver related to wifi. When I am looking its hex dump, I can see that it is including a path to one particular file of kernel headers. It is as under. 6C 75 65 2E 0A 00 00 00 25 64 2E 25 64 2E 25 64 lue.....%d.%d.%d 2D 25 73 00 00 00 00 00 42 45... (4 Replies)
Discussion started by: linuxdevnoob
4 Replies

5. IP Networking

Open Suse Router

Hello I am having some issues doing to routing I have 4 network cards and one is connected to a linksys router with everything turned off to give us a static ip to use for the gateway out to the internet. Hear is what we have We have eth2 with ip address of / sub (0 Replies)
Discussion started by: psutliff-una
0 Replies

6. UNIX for Dummies Questions & Answers

Adding SDK Build on Kernel Source Build

Hi, So I downloaded this kernel source and was able to build it successfully. But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself. I added the SDK in the main Makefile: init-y := init/ #added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies

7. Shell Programming and Scripting

Rm -rf file.txt~ included in the first step?

I need to shred and delete a file after a certain time. Therefore I use shred -z /path/to/file.txt | rm -rf /path/to/file.txtIt works well, but typing in that very directory ls -shiI still see the so called backup-copy lets say file.txt~ When running bleachbit it will disappear thoroughly.... (3 Replies)
Discussion started by: 1in10
3 Replies

8. SuSE

Personal SUSE build installation issues. I have created a personally made SUSE-based distro using and it will install just fine on my laptops (32-bit Acer Aspire One ZG5 and MacBook 4,1). However, when installing on an old Emachine desktop, I... (6 Replies)
Discussion started by: TheOuterLinux
6 Replies

9. Shell Programming and Scripting

Show file name included time information

Hi all, I have many files included time information, some of them included time range by 30 minutes; 2007-12-27T110000.txt 2007-12-27T120000.txt 2007-12-27T130000.txt 2007-12-27T150000.txt 2007-12-27T153000.txt 2007-12-28T000000.txt 2007-12-28T003000.txt I only want to echo that... (5 Replies)
Discussion started by: jeo_fb
5 Replies
SUBDOMAIN.CONF(5)						     AppArmor							 SUBDOMAIN.CONF(5)

/etc/apparmor/subdomain.conf - configuration file for fine-tuning the behavior of the AppArmor security tool. DESCRIPTION
The AppArmor security tool can be configured to have certain default behaviors based on configuration options set in subdomain.conf. There are two variables that can be set in subdomain.conf: SUBDOMAIN_PATH, and SUBDOMAIN_MODULE_PANIC. SUBDOMAIN_PATH This variable accepts a string (path), and is by default set to '/etc/apparmor.d/' This variable defines where the AppArmor security tool looks for its policy definitions (a.k.a. AppArmor profiles). SUBDOMAIN_MODULE_PANIC This variable accepts a string that is one of four values: warn, build, panic, or build-panic, and is set by default to warn. This setting controls the behavior of the AppArmor initscript if it cannot successfully load the AppArmor kernel module on startup. The four possible settings are: warn Log a failure message (the default behavior). build Attempt to build the AppArmor module against the currently running kernel. If the compilation is successful, the module will be loaded and AppArmor started; if the compilation fails, a failure message is logged. panic Log a failure message and drop to runlevel 1 (single user). build-panic Attempt to build the module against the running kernel (like build) and if the compilation fails, drop to runlevel 1 (single user). BUGS
Setting the initscript to recompile the module will fail on SUSE, as the module source is no longer installed by default. However, the module has been included with the SUSE kernel, so no rebuilding should be necessary. If you find any additional bugs, please report them at <http://>. SEE ALSO
apparmor(7), apparmor_parser(8), and <>. AppArmor 2.7.0~beta1 2010-12-20 SUBDOMAIN.CONF(5)

Featured Tech Videos

All times are GMT -4. The time now is 09:54 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy