Sponsored Content
Operating Systems Linux SuSE g++ build on SUSE 12.1, cannot open included file Post 302581710 by LMHmedchem on Tuesday 13th of December 2011 11:17:25 PM
Old 12-14-2011
Quote:
Originally Posted by jim mcnamara
It is probably a compiler issue. But I do not know either. strace can be used for this kind of thing. Sometimes.

This will produce a list of all syscalls involving file I/O. And their return codes, look for -1 return codes and the name of the error like ENOENT EPERM.
Code:
strace -e trace file -f -ff -o outputfilefromtrace  make -f mymakefile.mk

For a large build this may not be feasible, but it appears you are just building one tool set.
The -ff option creates separate files for each child process, you can then grep for -1

The candidate syscall most likely to fail is stat - stat is used to traverse PATH variables or -I dirname kinds of compiler directives.
In your case the last file in
Code:
 ls -lstr outputfilefromtrace*

contains the culprit's fingerprints.
This is an include inside of another included file, so I don't know if that is the problem, but I don't see how it could work some times and not others. I will look at the trace. I will also just manually add the included file, since the data is always there. I don't remember why this was a separate file in the first place.

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
strace(1M)						  System Administration Commands						strace(1M)

NAME
strace - print STREAMS trace messages SYNOPSIS
strace [ mid sid level...] DESCRIPTION
strace without arguments writes all STREAMS event trace messages from all drivers and modules to its standard output. These messages are obtained from the STREAMS log driver (see log(7D)). If arguments are provided, they must be in triplets of the form mid, sid, level, where mid is a STREAMS module ID number, sid is a sub-ID number, and level is a tracing priority level. Each triplet indicates that tracing messages are to be received from the given module/driver, sub-ID (usually indicating minor device), and priority level equal to, or less than the given level. The token all may be used for any member to indicate no restriction for that attribute. The format of each trace message output is: <seq> <time> <ticks> <level> <flags> <mid> <sid> <text> <seq> trace sequence number <time> time of message in hh:mm:ss <ticks> time of message in machine ticks since boot <level> tracing priority level <flags> E : message is also in the error log F : indicates a fatal error N : mail was sent to the system administrator (hardcoded as root) <mid> module ID number of source <sid> sub-ID number of source <text> formatted text of the trace message Once initiated, strace will continue to execute until terminated by the user. EXAMPLES
Example 1: A sample output of the strace command: The following example outputs all trace messages from the module or driver whose module ID is 41: strace 41 all all The following example outputs those trace messages from driver or module ID 41 with sub-IDs 0, 1, or 2: strace 41 0 1 41 1 1 41 2 0 Messages from sub-IDs 0 and 1 must have a tracing level less than or equal to 1. Those from sub-ID 2 must have a tracing level of 0. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5), log(7D) STREAMS Programming Guide NOTES
o There is no restriction to the number of strace processes opening the STREAMS log driver at a time. o The log-driver records the list of the triplets specified in the command invocation, and compares each potential trace message against this list to decide if it should be formatted and sent up to the strace process. Hence, long lists of triplets will have a greater impact on overall STREAMS performance. Running strace will have the most impact on the timing of the modules and drivers generating the trace messages that are sent to the strace process. If trace messages are generated faster than the strace process can handle them, some of the messages will be lost. This last case can be determined by examining the sequence numbers on the trace messages output. SunOS 5.10 4 Oct 1994 strace(1M)
All times are GMT -4. The time now is 05:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy