Sponsored Content
Full Discussion: Build using scons
Top Forums Shell Programming and Scripting Build using scons Post 302920706 by Aia on Saturday 11th of October 2014 01:40:55 PM
Old 10-11-2014
Quote:
Originally Posted by kristinu
The above produces errors

Code:
scons -f build/sc/botoh.sc
scons: Reading SConscript files ...
Could not locate endian.f
Could not locate botoh.f
scons: done reading SConscript files.
scons: Building targets ...
gfortran -o botoh.x -g
gfortran: fatal error: no input files; unwilling to write output files
compilation terminated.
scons: *** [botoh.x] Error 1
scons: building terminated because of errors.

That's not the same that scons -f /vik/build/sc/botoh.sc
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Problem during build

Hi, When i'm compiling my C files, I'm getting an error saying that the file name i've defined is undeclared. Could someone tell me how to solve this error. I've defined the file name as #define _FILE_CODE_ _XYZ_C_ The error is "_XYZ_C undeclared". Thanks in advance (1 Reply)
Discussion started by: laxmi
1 Replies

2. Emergency UNIX and Linux Support

Which OS Binary was build

We have recently installed RHEL 5.4 on some existing 6.2 OS and migrated our code from RH 6.2 to RHEL 5.4. We are facing a difficulty that given a binary (on both OS they have same name) how can we distinguish that which gcc and OS it was build as there are some minor differences in between binary... (2 Replies)
Discussion started by: uunniixx
2 Replies

3. Programming

Build Error

I am facing a problem while building the device driver code. I am using suse linux "2.6.31.5-0.1-desktop" on my Laptop. I have copied a folder containing self written device driver files from Mandriva linux to my system having Suse Linux. I copied the entire folder in "/home/netuser/sun/".... (4 Replies)
Discussion started by: rupeshkp728
4 Replies

4. Shell Programming and Scripting

Build failure

Hey everyone, I'm using Linux Mint Debian Edition Gnome, and I'm trying to add the Oracle JDK to the repositories using this simple script, which has never let me down before, but it keeps giving me this error every time I run it, here's my output: eddie_nygma@enigmatics ~ $ sudo ./oab-java.sh ... (0 Replies)
Discussion started by: Quizmaster
0 Replies

5. 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

6. Shell Programming and Scripting

Build.xml invocation by Build Script

Hi I have a build.xml file and I can run it on Windows via cmd. Now I want to write a script to invoke the same. Is there a way to do this? (1 Reply)
Discussion started by: ankur328
1 Replies

7. UNIX for Advanced & Expert Users

Using scons

I am trying to use scons to build a program in fortran 2008. I am using a makefile to build the program as follows all: /home/cdim/Local/gcc-4.9.0/bin/gfortran -ffree-form -c endian.f /home/cdim/Local/gcc-4.9.0/bin/gfortran -ffree-form -c testconvert.f ... (0 Replies)
Discussion started by: kristinu
0 Replies

8. Windows & DOS: Issues & Discussions

(VS 2008) New build config looking files from other folder build config

Hi Team, My new build configuration always looking for the files from the build where i copied from. please help me to resolve this. I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
locate(1)						      General Commands Manual							 locate(1)

NAME
locate - find files by name SYNOPSIS
locate [OPTION]... PATTERN... DESCRIPTION
locate reads one or more databases prepared by updatedb(8) and writes file names matching at least one of the PATTERNs to standard output, one per line. If --regex is not specified, PATTERNs can contain globbing characters. If any PATTERN contains no globbing characters, locate behaves as if the pattern were *PATTERN*. By default, locate does not check whether files found in database still exist. locate can never report files created after the most recent update of the relevant database. EXIT STATUS
locate exits with status 0 if any match was found or if locate was invoked with one of the --limit 0, --help, --statistics or --version options. If no match was found or a fatal error was encountered, locate exits with status 1. Errors encountered while reading a database are not fatal, search continues in other specified databases, if any. OPTIONS
-b, --basename Match only the base name against the specified patterns. This is the opposite of --wholename. -c, --count Instead of writing file names on standard output, write the number of matching entries only. -d, --database DBPATH Replace the default database with DBPATH. DBPATH is a :-separated list of database file names. If more than one --database option is specified, the resulting path is a concatenation of the separate paths. An empty database file name is replaced by the default database. A database file name - refers to the standard input. Note that a database can be read from the standard input only once. -e, --existing Print only entries that refer to files existing at the time locate is run. -L, --follow When checking whether files exist (if the --existing option is specified), follow trailing symbolic links. This causes broken sym- bolic links to be omitted from the output. This is the default behavior. The opposite can be specified using --nofollow. -h, --help Write a summary of the available options to standard output and exit successfully. -i, --ignore-case Ignore case distinctions when matching patterns. -l, --limit, -n LIMIT Exit successfully after finding LIMIT entries. If the --count option is specified, the resulting count is also limited to LIMIT. -m, --mmap Ignored, for compatibility with BSD and GNU locate. -P, --nofollow, -H When checking whether files exist (if the --existing option is specified), do not follow trailing symbolic links. This causes bro- ken symbolic links to be reported like other files. This is the opposite of --follow. -0, --null Separate the entries on output using the ASCII NUL character instead of writing each entry on a separate line. This option is designed for interoperability with the --null option of GNU xargs(1). -S, --statistics Write statistics about each read database to standard output instead of searching for files and exit successfully. -q, --quiet Write no messages about errors encountered while reading and processing databases. -r, --regexp REGEXP Search for a basic regexp REGEXP. No PATTERNs are allowed if this option is used, but this option can be specified multiple times. --regex Interpret all PATTERNs as extended regexps. -s, --stdio Ignored, for compatibility with BSD and GNU locate. -V, --version Write information about the version and licence of locate on standard output and exit successfully. -w, --wholename Match only the whole path name against the specified patterns. This is the default behavior. The opposite can be specified using --basename. EXAMPLES
To search for a file named exactly NAME (not *NAME*), use locate -b 'NAME' Because is a globbing character, this disables the implicit replacement of NAME by *NAME*. FILES
/var/lib/mlocate/mlocate.db The database searched by default. ENVIRONMENT
LOCATE_PATH Path to additional databases, added after the default database or the databases specified using the --database option. NOTES
The order in which the requested databases are processed is unspecified, which allows locate to reorder the database path for security rea- sons. locate attempts to be compatible to slocate (without the options used for creating databases) and GNU locate, in that order. This is the reason for the impractical default --follow option and for the confusing set of --regex and --regexp options. The short spelling of the -r option is incompatible to GNU locate, where it corresponds to the --regex option. Use the long option names to avoid confusion. The LOCATE_PATH environment variable replaces the default database in BSD and GNU locate, but it is added to other databases in this imple- mentation and slocate. AUTHOR
Miloslav Trmac <mitr@redhat.com> SEE ALSO
updatedb(8) mlocate Jul 2005 locate(1)
All times are GMT -4. The time now is 03:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy