Sponsored Content
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
Old 12-14-2011
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,
Code:
      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,
Code:
./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.

LMHmedchem
 

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 192.168.1.2 / sub 255.255.255.0... (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.

http://uploads.tapatalk-cdn.com/20160725/0174562490859032f68430fb0fa216cd.jpg I have created a personally made SUSE-based distro using susestudio.com 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
build(1)                                                      General Commands Manual                                                     build(1)

NAME
build - build SuSE Linux RPMs in a chroot environment SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm] build --help build --verify DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc- tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec file for example), even if the package does not use BuildRoot. build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec- tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be sufficient for the build. If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current directory. OPTIONS
--clean remove the build system and reinitialize it from scratch. --no-init skip the build system initialization and start with build immediately. --list-state list rpms that would be used to create a fresh build root. Does not create the build root or perform a build. --rpms path1:path2:path3... Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari- able. --arch arch1:arch2:arch3... What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify this option. --root buildroot Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable. --useusedforbuild Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the same packages used for the srcrpm build. --norootforbuild --help Print a short help text. --verify verify the files in an existing build system. .spec FILE OPTIONS The build command interprets some special control comments in the specfile: # norootforbuild # needsrootforbuild build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2, the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec- tively. # needsbinariesforbuild provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root. ENVIRONMENT
BUILD_ROOT The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default. BUILD_RPMS Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value which will do the trick if you have the SuSE Linux DVD mounted. BUILD_RPM_BUILD_STAGE The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip- tions. "-ba" is the default. You can use this to add more options to RPM. SEE ALSO
rpm(1), Maximum RPM: http://www.rpm.org/max-rpm/ cross distribution packaging: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to SUSE packaging standards and guidelines: http://en.opensuse.org/Packaging (c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)
All times are GMT -4. The time now is 11:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy