Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inappropriate path for intel-idb.conf and intel-fortran.conf #8

Open
Firef0x opened this issue Oct 7, 2014 · 0 comments
Open

Inappropriate path for intel-idb.conf and intel-fortran.conf #8

Firef0x opened this issue Oct 7, 2014 · 0 comments

Comments

@Firef0x
Copy link

Firef0x commented Oct 7, 2014

Since makepkg will change the current directory to $srcdir and symlink the source files to $srcdir automatically, the following lines could be changed like this:

Lines:
https://github.com/simon-r/intel-parallel-studio-xe/blob/master/PKGBUILD#L438
https://github.com/simon-r/intel-parallel-studio-xe/blob/master/PKGBUILD#L440
https://github.com/simon-r/intel-parallel-studio-xe/blob/master/PKGBUILD#L498
https://github.com/simon-r/intel-parallel-studio-xe/blob/master/PKGBUILD#L500

Example:
From:

sed 's/<arch>/ia32/' < ../intel-fortran.conf > ${xe_build_dir}/etc/ld.so.conf.d/intel-fortran.conf

To:

sed 's/<arch>/ia32/' < intel-fortran.conf > ${xe_build_dir}/etc/ld.so.conf.d/intel-fortran.conf

The change doesn't make sense to users who use makepkg to build it on their own computer. But for OpenSUSE Build Service, the former one results in error 'File intel-fortran.conf not found', while the latter one works good. Hence it makes sense to users who build it on OpenSUSE Build Service.

Hope for your reply!

Yours, sincerely

Refer to #5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant